04b | Manage Test Execution (2 of 2). Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM. Module Overview. Run Tests Perform Exploratory Testing Manage Bugs Use Lab Center Analyze Recommended Tests Perform Analysis Manage Work Items.
04b | Manage Test Execution (2 of 2)
Steven Borg | Co-founder & Strategist, Northwest Cadence
Anthony Borton | ALM Consultant, Enhance ALM
Use Lab Center
Development and Testing
Modern applications need to be deployed and tested in multiple environments.
Whether you store your test environments on bare metal or in the cloud, Lab Manager enables automation and increases collaboration, reducing the build-deploy-test cycle time.
When developers and testers collaborate, quality wins.
Developers build the application, deploy it to an environment and run automated test cases in a single step, preparing the way for testers.
Testers spin up environments to run manual tests, and test agents record all the data required to recreate any bugs.
Snapshot environments and attach to bug reports so developers can easily reproduce in the exact environment where the defect was found.
Enable data collectors and generate detailed test results to ensure any bugs that are found are actionable.
Team Foundation Server keeps track of all the pieces, keeping your entire team on the same page and reducing time to repair.
Analyze environments Recommended Tests
Perform Analysis environments
Microsoft Test Manager
Visual Studio IDE
Test planning and management
Test case management
Code quality analysis
UI automation testing
Microsoft Feedback Client
Team Foundation Server
Work item tracking
Lab management services
Test execution services
Reporting and BI
Diagnostic data collectors
Quality metrics and reporting
Role tailored tools feed data to transparent quality reports
Test Failure Analysis
Pre-built and fully customizable cross project reporting
The build report is a barometer of quality and a harbinger of success or failure.
As the development cycle nears the end, defects and failed builds should trend towards zero. Build quality reports provide teams clear insight into the development process and can indicate where teams need to focus their efforts.
Right out of the gate environments
Waiting until the end of a cycle to address defects can adversely impact schedule and resources.
Desired ATDD behavior should see a high spike in failing acceptance tests early in the cycle with the spike tapering down as the cycle progresses indicating that tests are being run early and uncovering defects early on.
Development teams can use defect tracking reports to estimate levels of deliverable code quality and to provide insight into a team’s ability to address defects.
A defect should ideally be detected and solved once, with a corresponding test implemented to ensure the fix addresses the desired behavior. Bug reactivations should remain close to zero.
Filling in the gaps
The only thing constant is change and code that changes must be tested.
To ensure your code base is fully covered by test leverage the code coverage report and identify your testing gaps. Establishing a code base fully covered by tests ensures new changes will not break your code!
I can see clearly now
A picture is worth a thousand words and a Stories Overview report gives that big picture!
The Stories Overview gives a comprehensive view of each implemented user story including completion status, test results and bug status. A thousand words, indeed!
uncovered, or partially covered by test
EXAM BEST BETS