Содержание
- 2. AGENDA
- 3. DEFINITION TEST CASE
- 4. A test case is a set of test inputs, execution conditions, and expected results developed for
- 5. TEST CASES GOALS
- 6. TEST CASES GOALS
- 7. FOR TEST CASES TOOLS
- 8. TOOLS FOR TEST CASES TestLink Jira
- 9. NO TOOLS? Use Excel
- 10. STRUCTURE TEST CASE
- 11. SOFTWARE TESTING METHODS STRUCTURE OF TEST CASES Required fields of a test case: Optional elements:
- 12. WHAT IS A GOOD TEST CASE? Specific or General? Positive or Negative? Simple or Complex? Independent
- 13. SPECIFIC OR GENERAL? Both tests cases test the same feature. What are the good and bad
- 14. SPECIFIC OR GENERAL? We are not tied to specific value We still know how to check
- 15. POSITIVE OR NEGATIVE? LEGACY What test cases will you create to test login to an application?
- 16. POSITIVE AND NEGATIVE AND BOUNDARY LEGACY Both positive and negative test cases are valuable.
- 17. SIMPLE OR COMPLEX? LEGACY Test scenario is a set of test cases for some purpose. Good
- 18. INDEPENDENT OR TIED TOGETHER? LEGACY Industry standard is stand-alone tests. Still it is ok to have
- 19. CREATION PROCESS TEST CASE
- 20. TWO STAGES
- 21. CHECKLIST
- 22. ‘PMC’ application 1. Login 2. Bugs 2.1 Bug details form 2.1.1 View details 2.1.2 Edit details
- 23. STEP 2 Start with “simple” tests 1. Login, valid Don’t forget about negative cases 2. Login,
- 24. STEP 3 Fill in Details, Resolve Questions
- 25. STEP 4 Add Cosmetics Add consistent numbering Correct any mistypes, spelling grammar Add Consistent formatting Edit
- 26. STEP 5 Get Review Get review from other tester, developer, customer Are some interesting tests missed?
- 27. Use active case, do this, do that Use “System displays this, does that” Use simple, conversational
- 29. Скачать презентацию