Yana Lysa "Best practices of building good manual test suits"
•
0 likes•403 views
Sometimes you read test case and understand, that something is wrong with it, but you can't understand what exactly. I want to share with you a list of pitfalls, that should be avoided during test suits preparation. There is a list of test design patterns, which I want to propose you to use to avoid making mistakes when writing manual test cases.
Recommended
Recommended
More Related Content
What's hot
What's hot (18)
Similar to Yana Lysa "Best practices of building good manual test suits"
Similar to Yana Lysa "Best practices of building good manual test suits" (20)
More from Fwdays
More from Fwdays (20)
Recently uploaded
Recently uploaded (20)
Yana Lysa "Best practices of building good manual test suits"
- 1. Best practices of building good manual test suitsmanual test suits Yana Lysa Access Softek, Inc.
- 2. About me QA work experience more than 7 years QA Lead experience 3 years Remote experience 4 years ISTQB certified Test Manager and TestISTQB certified Test Manager and Test Analyst Current position: QA Coordinator at Access Softek, Inc. lysaya.yana@gmail.com
- 3. Agenda 1. How test case can become bad 2. Possible reasons of bad test cases and suits 3. Pitfalls QA can face with during creation of test3. Pitfalls QA can face with during creation of test cases and building test suits 4. Tips and conclusions
- 4. Characteristics of bad test case Unclear, Ambiguous Duplicates Redundant workRedundant work Non-repeatability Lowmaintainability Bad feeling about it
- 5. Reasons of bad test cases appearance Incompetence CarelessnessInexperience Assumptions PitfallsInstability Time pressure
- 6. Pitfalls in test cases and suits building
- 7. Hello, twin brother Test case 46: Check received email … Step 6. Send email Step 7. Check, that user received email … Test case 64: Check ability to send email
- 8. Hello, twin brother Pitfalls Already tested or covered Duplicates covered Solutions Traceability Planning Collaboration
- 9. Tops and roots Create new PayPal transfer Create new Check withdrawal transferCreate new Check withdrawal transfer Create new business transfer Check transfer history for business user Check transfer history for private user …
- 10. Tops and roots Pitfalls Only titles Description of business scenario No expected results Solutions Traceability Add expected results
- 11. Trainee-oriented test cases Open application Expected result… Click on Login button Expected result… Enter test@test.com in Email field Expected result… Enter “test” in Password field Expected result… Click on “Login” button Expected result…
- 12. Trainee-oriented test cases Pitfalls Full navigation Too much explanations Repeating Solutions Pre- conditions Test cases calls Cross-review
- 13. Too much negativityToo much negativity Save patient’s age field with empty value; Expected result: not possibleExpected result: not possible Save patient’s age field with alphabetic characters Expected result: not possible Save patient’s age field with special characters Expected result: not possible Save patient’s age field with ‘NULL’ Expected result: not possible Save patient’s age field with ‘999999999999999’ Expected result: not possible Save patient’s age field with negative value Expected result: not possible
- 14. Too much negativity Pitfalls Copy- paste most of case One expected result for many test casescase cases Solutions Combine Use parameters Checklists
- 15. Steps, steps, steps… Step 1. Login as application user Expected result…Step 1. Login as application user Expected result… Step 2. Start creation of task Expected result… Step 3. Enter task name Expected result… Step 4. Enter Due date Expected result… Step 5. Enter task description Expected result… … Step 26. Select task watchers Expected result… Step 27. Click on “Create” button Expected result…
- 16. Steps, steps, steps… Separate step CombinationSeparate step for every action Combination of steps with no effect
- 17. Bulk steps Step 1. Open application. Login with correct credentials as application user. Navigate to Files menu. Click on “Create new folder” button and create new folder Expected result: Folder with name specified is created Step 2. Open created folder. Click on “Upload file” button. Select file from computer. Click on “Select” button. Expected result: File is uploaded
- 18. Bulk steps A lot of steps in one action Losing big picture Combine one action
- 19. Endless call Step 1. <<Registration>> Expected result: <<Successful registration>> @REG_DATA Step 2. <<Fill user profile>> Expected result: <<Successful message>> Step 3. <<Upload user picture>> Expected result: <<Successful picture upload>> …
- 20. Endless call Pitfalls Too many calls of parameters/tests Big picture is lost Solutions Call only shared test cases Cross-review
- 21. Test case to the moon and back1. Login as private user 2. Create new transfer to business user 3. Enter… 10. Navigate to History 11. Check balance 12. Navigate to Account list 13. Check balance … 22. Logout 23. Login as business user 24. Check balance of account, where transfer was sent … 25. Login as admin user 26. Check ability to cancel created transfer … 45. Connect to DB 46. Check that correct value is written in DB
- 22. Test case to the moon and back Pitfalls Everything in one case There is always something failfail Solutions 1 test case = 1 test goal Use test suits instead of long test case
- 23. You can call me as you wish Step 1. Click on “Table” menu Expected result: Menu is opened Step 2. Push “Board” switcher Expected result: User is navigated to “Board” window Step 3. Press on “Table” button Expected result: “Table” screen is displayed
- 24. You can call me as you wish Pitfalls No terminology standardization Inconsistent user actions Solutions Standard for terminology Glossary with user actions
- 25. Magic test Step 1. Login as manager Step 2. Invite new team member Step 3. Login as new team member Step 4. Create new task as newStep 4. Create new task as new team member Step 5. Reject new task as manager
- 26. Magic test Pitfalls Steps are unclear or have no goal Lack of explanation how to get from A to B Unneeded complexity from A to B Solutions Plan Cross-review
- 27. Tips of test suits design • Use test design techniques; • Traceability to requirements; • 1 test case=1 goal; • Big test cases split and combine in test suits; • Use pre-conditions and common explanations; • Use parameters, if it is possible;• Use parameters, if it is possible; • Use checklists, when possible; • Use parameters; • Use test data separately from test case; • Plan test suit structure; • Use standardization; • Combine steps having same expected result; • Cross-review.
- 28. Conclusion • Plan your test suits; • Build traceability to requirements; • Find right balance of details and parameters,• Find right balance of details and parameters, imagination and negative cases, etc.; • Cross-review.
- 29. Questions? • LinkedIn: linkedin.com/in/yana-lysa-4b3b4667 • Email: lysaya.yana@gmail.com• Email: lysaya.yana@gmail.com