-
Notifications
You must be signed in to change notification settings - Fork 14
Create Test Execution Strategy document #318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Added a comprehensive Test Execution Strategy document covering objectives, phases, and prioritization.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Updated the Test Execution document to enhance structure and clarity, including objectives, phases, and prioritization strategies.
| ### Manual Testing | ||
| - Run Manual Tests using Azure DevOps Test Execution Tool | ||
| - Add results for each test case | ||
| - Add & Attach Test result screenshot for test steps that prove the testcase has passed to each testcase for clear traceability |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iNileshW - did we not say this up to to the test team to decide how they will capture test results?
RaviK2233
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iNileshW - please see comments
Removed reference to Jira for defect logging.
Added a comprehensive Test Execution Strategy document covering objectives, phases, and prioritization.