Test execution improvements – Apr 2016
About a month ago, I published a blog detailing Testing tools roadmap and the value we have delivered over the last six months. If you have not seen it yet, I will encourage you to read and provide feedback. We continue to focus on efficient test execution across automated, manual and exploratory testing scenarios. Here are some enhancements that we intend to deliver in the next 6 months:
NOTE: As with any roadmap, timeline is subject to change and designs below are early mockups to illustrate concepts.
MStest convergence : DONE. Please find more information here
We are consolidating many variants of MStest into a single variant that works across different application platforms – Win32, Phone, UWP, ASP.NET Core 1.0, and .NET Core. This consolidation will bring in one of the highest asked items on UserVoice (DataRow support), a clean end-user extensibility mechanism, and a single codebase to evolve.
Test explorer enhancements: We have been getting lots of feedback on improving VS IDE test explorer experience on UserVoice – we are starting with a few important ones and will continue to work on others to make it more usable.
- Open the Test Explorer window immediately after tests are run (especially when run from the code editor window)
- Enable select-and-copy from the test details pane
- Enable select-and-copy from the Test Output window in the Test Explorer
- Fix test duration reporting
- Don’t ask to run the test from previous build if build fails
Flaky tests and test history: We will make it easy for you to identify flaky tests and provide test results history across all workflows, various branches and environments.
Test History: DONE
BDT support for Azure, SCVMM and VMWare environments: DONE.
We now have in-built tasks in CI/RM workflows to dynamically provision VMs and take appropriate actions like start, stop, snapshot, restore etc. You can leverage these tasks to create powerful BDT workflows for your needs. This should enable you to bring MTM and XAML based BDT workflows forward.
Insights across Exploratory Testing sessions: DONE.
You can view all the exploratory sessions your team has completed in the Runs hub in Test Hub group. You can group your sessions by the user stories explored, sessions or session owners and gather additional insights.
Feedback mode in Exploratory Testing extension: We plan to extend the Exploratory testing browser extension to include “feedback” mode targeted at Stakeholders. In this mode, stakeholders can provide feedback responses to solicited feedback or submit voluntary feedback for the engineering teams to process.
Load testing: DONE.
We intend to deliver a compelling Import/Create – execute – analyze web experience for all VSTS and Azure App Service Plan customers. We will enhance the reporting capabilities to include run-over-run comparisons. You will be able to create load tests using HTTP archive, Fiddler traces or by importing a VS web test. You can also bring your own load test rig either on premises or on Azure IaaS and use it with cloud load testing service. Similar to VSTS CI/RM tasks, Azure app service customers will be able to include performance tests as part of their deployment pipeline.