Creating TestCase

Ministry of Testing

Case Study:

Hi, I just wanna ask how you managed your time in creating test cases and testing at the same time if you only have 2 weeks in every sprint? Sometimes I don’t have time to finish my test case and start testing without a step by step test case, I only have the expected results in every user stories. TIA! btw, I do manual testing in agile development.

sometimes when I’m done creating my test case and devs raise something some of the requirements were changed and I need to update my test case again then suddenly devs are already done developing.

-- Anonymous

Recommendation 1:

1.Once sprint started you have time to write test cases until the task ready for the tests. Based on scenarios you can prepare 50% of your tests.

2. prioritize you work allocate every day some time to prepare test case

3. Mention in retro about your difficulties.

-- Pramod Mandapati

Recommendation 2:

I try to write TCs or document strategy before the Refinement, and update them as the story & discussion progresses. I do a final review / update the week or sprint before the scheduled sprint.

-- Bhavani Krithivasan

Recommendation 3:

In my company, we found we had to balance the number of testers on each sprint team with the number of developers so the testers have time to not only write / update test cases but also write automation. If there's not enough time to write your test cases as well as do testing, you may need another tester on the team.

I tend to write basic test cases as I test, documenting what I do as I go, and if a test case isn't already written my notes are the draft for that case. It saves time. For comparison, my team has three developers (1 is senior) and 2 QA. When my team only had one QA (me) I was tearing my hair out. I made the case with management over and over until they gave our team a second QA. Now testing keeps up with development.

It depends on the velocity the developers and QA can keep up. In my company 3 devs and 2 qa tends to work out well. 4 devs and 2 qa can work well if the devs are cross functional and can help out with automated test writing.

-- Tracey Clark

Reference:

Test Cases Are Not TestingSatisfice, Inc.

This may be my all-time favourite error messageDevelopsense Blog

“Manual” and “Automated” TestingDevelopsense Blog

The End of Manual TestingDevelopsense Blog

Testing Problems Are Test ResultsDevelopsense Blog