Peer Review and Peer Approval process

 

1. Peer Review process

2. Peer Approval process  

   
   
   

 

 

 

Build & Implement standards for writing testcases

What Is a Test Case in Software?

A test case is exactly what it sounds like: a test scenario measuring functionality across a set of actions or conditions to verify the expected result. 

 Standards/ Random ideas for writing a testcase:  

1. Find the right master suite for a test case in your test management studio . Create a new suite if needed. 
    

2. Mention Right Area path and Iteration for a test case (Area path and Iteration are terms used in Azure DevOps. )

3. Maintain the title of a test case as per QC standards of your Company
    

4. The title needs to be precise and easily readable as per project. Feature, sub-feature and verification statement  

5. Manage Order of Testcases for easy execution of test cases. This will be helpful for Integration and System testing for a tester.  

6. Build Link for all Test cases so the team can generate the reports.  

7. Use shared steps if needed. Create a new one if needed.  

1. Name of shared steps – Testcase name (Shared) 
    

8. Manage the stage of testcases. Assign for peer review. 

9. Mention any success / alert message, title & sub title, form labels in double quotes and italics 

10. Mention verification Statement in bold   

11. Mention expected result for each steps as per need of spec
    

12. Mention time estimates a test case if possible 

13. Use keywords “Navigate” for page/ screen navigation  

14. Mention hardware actions as required for a test step 

15. Mention “Manual Setup” or manual database intervention as bold letters