Enroll into QATUTOR Video Course on 

Questions & Exercises

Lecture 3 - Test Cases and Test Suites -> Quick Intro -> Test Case Structure -> Results Of The Test Case Execution -> Useful Attributes Of The Test Case -> Data-Driven Test Cases -> Maintainability Of Test Cases -> The Number Of Expected Results Inside One Test Case -> Bad Test Case Practices -> Test Suites -> States Of A Test Case -> The Importance Of Creativity -> Three Important Factors That Affect Test Cases -> Checklists -> Lecture Recap -> Questions & Exercises -> Self-Check Quiz 3

1. Name one part of a test case without which the test case cannot exist.

2. Why do we need steps in a test case?

3. List the results of a test case execution. Which result is desirable for us as testers?

4. What shall we do if the test execution is blocked?

5. Why should a test case have only one IDEA?

6. List the useful attributes of a test case and substantiate why shall we love and foster each of those attributes.

7. Do we change the test case ID if we change the test case and/or move the test case to another test suite?

8. Develop your own way create a test case ID (e.g., the spec ID can be a part of the test case ID).

9. What is a data-driven test case? Is it harder or easier to maintain a test case after we convert it into a data-driven format?

10. Why does test case maintainability save time?

11. List bad practices during test case generation/modification. Why should we avoid such practices?

12. Why is it a good practice to create a separate test suite for each new spec?

13. Is it expected that the tester will revise his freshly baked test cases?

14. Which criteria can we use to put test cases into the same test suite?

15. List the attributes of the test suite header.

16. List the states of a test case.

17. Why is it not recommended to permanently delete test cases?

18. Do we have some kind of set-in-stone standard for the test case format?

19. What is the difference between a test case IDEA and an expected result?

20. Write a test case with one IDEA and two expected results. Use a situation from everyday life. Next ->

Lecture 3 - Test Cases and Test Suites -> Quick Intro -> Test Case Structure -> Results Of The Test Case Execution -> Useful Attributes Of The Test Case -> Data-Driven Test Cases -> Maintainability Of Test Cases -> The Number Of Expected Results Inside One Test Case -> Bad Test Case Practices -> Test Suites -> States Of A Test Case -> The Importance Of Creativity -> Three Important Factors That Affect Test Cases -> Checklists -> Lecture Recap -> Questions & Exercises -> Self-Check Quiz 3