Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (18)
Semelhante a Commonly Held Beliefs about Test Cases v1.0
Semelhante a Commonly Held Beliefs about Test Cases v1.0 (20)
Commonly Held Beliefs about Test Cases v1.0
- 1. Commonly Held Beliefs about Test Cases Dave Bell
- 2. Objectives • Open up your mind • Examine different approaches • Achieve better testing results • Satisfy our customers
- 3. Today’s Tester .. Of Range of Quality The ‘Test’ Step 2. Written Step 1. Thought of Step 3. Executed To … Find defects that matter Identify risks Help managers make ship / no- ship decisions Assess quality Assess conformance to specification Learn how the system works
- 4. Can testing only be done with test cases? It is common practice to write down detailed steps and then execute them We can use structured approach for review and re-use BUT Can achieve testing goals with exploratory testing as well as checks The Business wants to know that the bugs that matter to them are are addressed or identified, not that you had test cases We should select the best approach for testing in our context
- 5. Will I find all defects with test cases? I have detailed expected results to check against system Designs have re-inforced how the system should / should not behave BUT The executed test cases may only enable finding defects by ‘checking’ The test case could be wrong, out of date or miss some key areas We should use our minds to experiment and check in a controlled way
- 6. Will my test cases achieve 100% coverage? We can write appropriate test cases to cover all requirements based on priority We can report on metrics for this BUT The world is not perfect and requirements may not be as well The tester needs to find undocumented requirements by questioning We should plan testing based on quality not quantity of information
- 7. Scripted and Exploratory Testing
- 8. Summary The tester needs to examine the best way to test in their context The tester should consider the balance between tools, checking and exploratory testing
- 9. Some resources James Bach’s blog post http://www.satisfice.com/blog/archives/856 http://www.satisfice.com/blog/archives/1509
Notas do Editor
- On a recent engagement, I was asked to write test cases however I felt I had a better way. I asked why? The manager of testing said “so that someone else can execute them if needed’. Is this sufficient reason for them? They weren’t to help ‘me’ test.
- I am sure you already know this. Today’s tester has a lot to do to accomplish their objectives for a given project, and must be able to adapt. One component of their role is the creation of tests. This presentation has been drafted to ask 3 questions of commonly held beliefs which may help us consider what decisions to make, question or influence, when creating these tests.
- Here is our first question to consider. Can testing be done without what we commonly refer to as test cases? Remember that it may seem that “Testing without Test Cases is like a car without an engine”. However, there is more than 1 way to build a car.
- We can demonstrate that the test cases we ran at that time did not identify any more defects. We cannot however prove the lack of existence of defects. We should set our minds to examine the system sufficiently to maximise our processes to raise the defects that matter.
- Recent example – tester said ‘couldn’t write tests as didn’t have detailed requirements’
- For a given engagement, we should ask ourselves the question: Should I use scripted test cases or exploratory testing?
- Test objects are only a part of what is needed in a tester’s toolkit How to find the best solution? How can you make the best judgement?