Posts
Testing costs time and money, and no doubts adds value. Then how do we get a balanced approach on testing the user stories..
These questions should be answered while writing automated test for Acceptance critera
1) Is it too low level of testing...?
- Do I really need to check a particular link is present or not...?
2) Are there repeating tests with some diversity?
- Can it be compromised over quick turnaround of the build?
3) How do we mitigate the risk of writing less tests?
- Can we make tests precise ?
- Can we not automate unit level tests in Accpetance test.
To be continued...
Nice article, +1
I agree to the point. But its always difficult to set boundaries in acceptance tests. I think this decision is more contextual then a generic pattern.
I agree with your point that up to what limit one has to test. But while designing test cases all the possibilities are covered that what we all called a good test case design. Software Testing Services