What do you mean by regression testing and what is the Regression Testing Meaning in Agile projects? We will explore the regression testing definition in software testing and see how it affects the Scrum developer role.
Estimating Scrum Tasks
A 59 Seconds Agile Video Animation
Regression Testing Definition in Software Testing – Part 2
A 59 Seconds Agile Article
Regression Testing Definition in Software Testing: Developer Role in Regression Testing
While the entire Scrum team works together to handle regression testing, what do the developers do for the process? Testing is normally handled by quality assurance technicians. Developers just write new code, so why should they care about regression testing?
When writing new code, developers need to be mindful of how old code works. By gaining a full understanding of how the foundation code works, developers can make changes without breaking old features. This can be done in a number of different ways. If there is a technical specification for a feature, developers should be careful to follow it closely. Even in the absence of a spec, developers might consult the previous developer for a feature. To avoid breaking code, one developer could ask the previous developer for insight on a program to see how it works. This reduces the risk of breaking functionality that a developer doesn’t understand.
Regression Testing Definition in Software Testing: New Code Commits
Before committing new code to a repository, developers should test related features. Just because a feature they’ve added or created works, doesn’t mean that other features in a program still do. It is best to run through these quickly, to avoid easily detected errors. While quality assurance technicians do most of the serious testing, catching errors before software goes to QA can also save time.
Regression Testing Definition in Software Testing: The Benefits
Regression testing is beneficial to any form of product development, including Scrum teams (Scrum Master, Product Owner and Development Team) in Agile development. Even though developers are typically not responsible for testing, they have an important role in regression testing. If developers do their part to minimize errors and fix issues quickly, it improves the software overall and saves time for everyone on a Scrum team.
User Stories Applied
A 59 Seconds Agile Book Review
User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.
Estimating Scrum User Stories
A 59 Seconds Agile Infographic
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum: