What is the way forward after Coded UI deprecation

What we will do after Coded UI deprecation?

Most of us are aware about Microsoft official announcement that Coded UI will no longer be available after Visual Studio 2019. This news triggers the question for those teams who are using Coded UI, what they will do? We have listed down here some points that might help to take a decision.

Why Microsoft is deprecating Coded UI Test?

Coded UI tests are used for UI-driven functional automation of web apps and desktop apps. Open source UI testing tools such as Selenium and Appium have gained momentum in recent years, have a strong community backing and are now pretty much industry standards. Coded UI’s cross-browser testing solution was itself based on Selenium. Additionally, both Selenium and Appium work cross-platform and support multiple programming languages.

Other important point is that Test automation focus is also shifting from predominantly UI driven testing to more unit testing and API testing.

For how long Microsoft will support?

Coded UI test in Visual Studio 2019 will continue to be supported for any issues that may arise during the support lifecycle of the product. As outlined in the product lifecycle and servicing documentation, you can continue to use Coded UI and will be fully supported for the next 5 years and an additional 5 years of extended support is also available should you need it. But this is limited to specific bug fixes, no new features will be added.

Will the test team able to maintain existing scripts?

Different Visual Studio versions can be installed side by side. This means that developers will be able to continue to use Visual Studio 2019 to maintain any existing Coded UI test assets, while being able to use any new Visual Studio versions when they becomes available in the future for other development needs.

What about the CI/CD pipeline in Azure DevOps?

The same side-by-side installation mechanism mentioned in above point, allows for CI/CD pipelines to keep running smoothly without any interruptions while you migrate. This is because when Coded UI tests run as part of a CI/CD pipeline in Azure DevOps, tests are run against a particular Visual Studio version installed on the agent or a particular version of test platform. We will continue to support running tests against Visual Studio 2019 or its associated test platform in newer versions of Azure DevOps until the support life cycle of Visual Studio 2019 ends.

Recommendation from Microsoft for migration

Microsoft recommend that any new test collateral being built should use the alternatives and plan your replacement of older Coded UI tests so that it is completed before the end of the Visual Studio support lifecycle. As part of this process it is recommend that customer re-evaluate their test portfolio to remove tests that are no-longer useful.

They recommend using Selenium for testing web apps and Appium with WinAppDriver for testing desktop and UWP apps. Consider Xamarin.UITest for testing iOS and Android apps using the NUnit test framework.

References:

https://devblogs.microsoft.com/devops/changes-to-coded-ui-test-in-visual-studio-2019/

Comments

Post a Comment

Popular Posts

How to Import and Export Delimited Files, like CSV, in PowerShell

Image
In this tutorial, we will see how we can use PowerShell to import and export CSV file's data. Managing CSV Files using Import/Export-CSV in PowerShell We have two important cmdlets import-csv/export-csv which are widely used while working with CSV. Before moving to how to manage these type of files, First look at what is CSV file: A Comma Separated Values ( CSV ) file is a plain text file that contains a list of data. These files are often used for exchanging data between different applications. For example, databases and contact managers often support CSV files. A CSV file has a fairly simple structure. It’s a list of data separated by commas as you can see in below screenshot. We have file "email.csv" having email address and name separated by comma. You can use notepad/excel to open thses file. Now lets move back to our main topic, how to manage csv files with PowerShell.  Reading CSV Files with Import-Csv Importing of csv file is pretty straight forward. First move to
Read more

PowerShell Arithmetic Operators

Image
In this tutorial we will see about PowerShell Arithmetic Operators and how PowerShell is dealing with them. Arithmetic operators are used to perform numeric calculations. As well as numeric calculations, the addition operator may also be used with strings, arrays, and hashtables. Multiplication operator may also be used with strings and arrays. Below is the list of PowerShell arithmetic operators. Operator Description Example + Adds numeric values 4 + 6 concatenates a string, arrays, and hash tables “CS” + “Tutorials” – Subtracts numeric values 4 – 2 Makes a number negative -98 * Multiple numeric values 4 * 2 copy string, arrays to the specified number of times “!” * 4 / Divides numeric values 4 / 2 % Gives remainder after division 7 % 3 For live demo, watch below video. I have demonstrated the use of PowerShell arithmetic operators by  creating calculator. Along with operators, Switch statement and While loop also used.  
Read more

How to generate a GUID in PowerShell

Image
 If you ever need a unique id in your script, you can create GUID (globally unique identifier) In PowerShell 4.0 and earlier you can use [guid] class with its static method. In PowerShell 5.0 and later, you can use New-Guid cmdlet: You can use Get-Member to know its object type. You can also store GUID into a variable like below If you want to get GUID as string, use ToString  method or Guid  property. Both return output of string type, you can verify this using Get-Member .
Read more