We've been recommending for a while that customers use the open source tools Selenium and Appium tools, therefore the Visual Studio 2019 release marks their final deprecation.
We recommend using Selenium for testing web-applications and Appium with WinAppDriver for testing desktop (WPF, WinForms, Win32) and UWP apps.
‘Run Functional Tests’ (RFT) task is used for running functional tests using remote machines or to run tests in a distributed manner using multiple machines. With TFS 2017 Update 2 and VSTS, You can use “Run Functional Tests” task to run tests using Visual Studio Test Agent 2017.
Visual Studio Test (VSTest) and the Run Functional Test (RFT) tasks are used widely for continuous testing with Team Build and Release Management. As we thought about how test execution in the pipeline should evolve the guiding principles were to ensure that test execution in the pipeline is fast and reliable for all types of tests,
There have been several questions on the different scenarios related to running automated tests in various workflows and which versions can / cannot be used.
Let’s use the following 2 names for categorizing how agents get used:
Test Controller/Test Agent (TC/TA) scenarios –
Update – As of Feb 24th 2017, this issue has been addressed and the content below is no longer applicable.
If you use Application Insights to collect app side metrics during load tests, you will find that it currently doesn’t work as expected.
Every now and then we hear of a business-critical app failing during major promotional or seasonal events such as holiday sales. More often than not it turns out that the app is not ready for the massive demand created on such occasions –
When you run a cloud-based load test, the load testing service automatically provisions the necessary machines (load agents) for generating the load to your application. Once the load test run has completed, these resources are torn down. This works well for the most part for a large set of customers.
Validating application’s performance by running a load test typically follows a test->fix->test loop, often repeated several times. After you have run an initial load test and made some changes (either on the app side or test side by fixing issues or tweaking configurations),
Did you know that you can use the cloud-based load testing service in VSTS to create and run load tests using HTTP archive (.har) files? The feature preview is available now. To learn more, see this link.
This blog post covers how to troubleshoot any request failures that may be happening in your test.
If you have used cloud-based load testing before, you may already be familiar with the ability to run a ‘quick load test’ using the VSTS portal. It’s a great way to:
Run a quick load test for your app – you just need to enter the app URL.
