Need of regression testing

Answer 1

->Understand your business area. This includes working with business partners and stakeholders to ensure each subset of the business area supported is documented and tracked by the team. Leverage subject matter experts (SMEs) from not only the testing organization, but also the business and development teams.

->Create, validate and maintain the artifacts. Simply documenting various integration points and subsets of business areas is not the only goal. It is important that, as new releases, updates and changes are rolled out, the suite is revisited and artifacts are updated to maintain the accurate and detailed picture of the business area.

->Understand the test cases required to build high coverage for the business area. It is important that you review this with the business stakeholders, development and testing teams to ensure agreement and collaboration between the teams. Creating test cases builds the framework for future savings as the test cases are created once in order to be used many times down the road.

->Build the test suite in priority order. Teams are able to quickly define which subsets of a business area are the most critical to the organization. Based on this prioritization, the test suites must be built in this order. NOTE: Do not confuse "prioritization" with "risk." Risk-based Testing does not apply to regression prioritization. After a regression test suite is built, teams may find not all regression test cases can be run at times, and a risk based approach must be followed. When this occurs, regression prioritization should be based on the importance of the test cases and whether these cases can detect and identify possible defects in the product.

->Just Start It! Nike had an extremely popular ad campaign in 1988 that carried the slogan, "Just Do It!" For regression test suites, the goal is to "Just Start It!" How you can apply this theory is to begin immediately using regression test suites the moment the first test cases are delivered. Begin experimenting with the test cases, building a lessons learned document, validating with the stakeholders that the quality of the test cases are mapped to the expected results. This ensures that the organization begins benefiting early from the initial regression efforts.