Teams are moving to a scrum type sprint. We understand the sprint mechanics for story pointing and committing to user stories etc - but cant wrap our heads around how we would handle a large manual regression within the sprint team/process? Automation isnt available right now but will be in the future (but need to plan for the now).
Would we create a regression user story and point that? if the points are large enough that the qa would only be able to achieve that in a full sprint what do the rest of the team do. I understand we would be better off releasing in smaller increments but again - have to have a plan for the now and move over time.
When we ask for suggestions, we are being told we can work it whoever it works best for the team BUT we are having difficulty envisioning the ways we could go to make a choice.
Handling manual regression testing in a sprint when automation is not available involves the following mechanics:
Time Allocation: Reserve a specific portion of the sprint for manual regression testing. This time should be based on the complexity of changes made during the sprint and the availability of resources.
Test Case Selection: Identify critical test cases from your existing test suite. These test cases should cover the most important and frequently used functionality of the software. Execute these test cases manually.
Test Suite Maintenance: Maintain a well-organized and up-to-date test suite that documents test cases, their expected outcomes, and steps to reproduce them. This suite serves as a reference for manual testers.
Effective Communication: Ensure open and effective communication within the development team. Developers should inform testers about the changes they've made and any potential areas of impact.
Defect Reporting: If manual testers discover defects during the regression testing, these issues should be reported promptly to the development team for resolution. The goal is to address defects within the same sprint to prevent the accumulation of technical debt.
By following these mechanics, you can integrate manual regression testing effectively into your sprint, ensuring that the software remains stable and functional despite the absence of automation.
As you are following Sprint methodology for software development, it would be very difficult to execute all the Regression test cases within 2 / 3 / 4 weeks of Sprint.
I would suggest maintaining good traceability matrix, covering Requirements -> Code -> Test cases, and based on the impact to the code/module, you can plan for focused regression testing around the impacted areas to certify the build.
You can also plan to have dedicated Regression sprint, may be after 4th or 5th Sprint (Testing Sprint, it may not be equal to the duration of your sprint, may be a week Sprint) where all the Scrum members participate including Product owners, Designers, Developers etc. which will help you to identify regression defects.
Let me know if you have more questions. Thanks.
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.