KEMBAR78
Regression Testing Notes | PDF
Scribd
Upload
6 views1 page

Regression Testing Notes

Microsoft Test Manager (MTM) manages the entire test lifecycle, including test planning, design, execution, and reporting. It supports bug logging and regression testing to ensure recent changes do not affect existing functionality. Key methods in regression testing include retesting all cases, selecting impacted tests, and prioritizing critical areas to balance cost, time, and quality.

Uploaded by

M HaroonF
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views1 page

Regression Testing Notes

Microsoft Test Manager (MTM) manages the entire test lifecycle, including test planning, design, execution, and reporting. It supports bug logging and regression testing to ensure recent changes do not affect existing functionality. Key methods in regression testing include retesting all cases, selecting impacted tests, and prioritizing critical areas to balance cost, time, and quality.

Uploaded by

M HaroonF
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Test Execution using Microsoft Test Manager (MTM)

Microsoft Test Manager (MTM) is used for managing the entire test lifecycle. It includes: 1. Test
Plan Development: Creating a structured plan for testing activities. 2. Test Design: Designing the
actual test cases and scenarios. 3. Test Execution: Running test cases to identify bugs. 4. Exit
Plan: Defining when to stop testing. 5. Test Reporting Plan: Planning how results will be captured
and reported. MTM helps from planning to reporting all test activities, including recording
executions.

Test Execution Reporting and Bug Logging

After executing test cases, bugs are logged and discussed. Developers may reject some bugs
during review meetings if the system is working as expected. MTM supports: 1. Execution Reports
2. Bug Logs 3. Test Cycle Closure

Regression Testing

Regression testing ensures that recent code changes haven't broken existing functionality. This
process is important especially after bug fixes, feature updates, or performance improvements. Key
points: - Retest only affected areas (not the whole system). - Select specific test cases relevant to
the changes. - Useful when full testing is too costly or time-consuming. Types of Regression
Testing: - Retest All: Re-run all test cases (expensive). - Regression Test Selection: Only selected
cases. - Test Case Prioritization: Focus on most critical areas. Importance: - Detect side effects of
new changes. - Minimize cost and time by smart selection.

Factors Affecting Regression Testing

Regression testing is required after: 1. Evolving requirements (add/update/delete). 2. Bug fixes. 3.


Client-requested changes. 4. Code recompilation. Considerations: - Critical applications (e.g.,
medical systems) need full retesting. - Commercial software may only need partial retesting. -
Always balance between cost, time, and quality.

Methods in Regression Testing

Key methods: 1. Retest All: Test everything again (costly). 2. Regression Test Selection: Only test
impacted parts. 3. Prioritization: Choose critical test cases first. Goals: - Reduce cost and effort. -
Maintain high quality. - Use recorded test cases to streamline testing.

You might also like