MSTest Tutorial: Running First Selenium Automation Script
MSTest Tutorial: Running First Selenium Automation Script
Parameterized tests allows tester to run the same test a few times using different values. Find out how you can do this in MSTest/
Join the DZone community and get the full member experience.Join For Free
MSTest is the default test automation framework which comes bundled with Visual Studio. It started as a command-line tool for executing tests and was referred to as the Visual Studio Unit Testing Framework; however, the name MSTest is more synonymous with the developers.
In the previous MSTest tutorial, I had a look at setting up the MSTest framework in Visual Studio. In this MSTest tutorial for Selenium automation, I’ll help you run your first MSTest script for automated web testing with Selenium C#.
Requirements For Running Your First MSTest Script
In this MSTest tutorial, I'll use the Chrome browser to verify the functionalities in the code. So, you’ll need to install the Chrome WebDriver on the machine where you’ve installed the MSTest framework and Selenium WebDriver.
Different web browsers have their corresponding Selenium WebDrivers. These WebDrivers are crucial to interact with the web elements on a page for automated web testing with Selenium C#. You can download the Selenium WebDriver for browsers such as Opera, Firefox, Chrome, Internet Explorer, Microsoft Edge, etc. using the following links.
Since I’ll be using Chrome, I’ll download the Selenium WebDriver for Chrome i.e. ChromeDriver. Though the downloaded ChromeDriver can be placed in any directory, it is a good practice to install the ChromeDriver in the location where the Chrome browser (i.e. Chrome.exe) is present. Learn more about running an automated test with Chromedriver.
The advantage of following this practice is that you do not need to specify the path where the ChromeDriver is present while invoking the WebDriver.
How To Run MSTest Scripts With Selenium?
For demonstrating the usage of Selenium WebDriver with MSTest, I’ll use the following Selenium test automation scenario for this MSTest tutorial:
1. Navigate to the URL https://lambdatest.github.io/sample-todo-app/
2. Select the first two checkboxes
3. Send ‘Adding item to the list’ to the textbox with id = sampletodotext
4. Click the Add Button and verify whether the text has been added or not
Implementation Of The MSTest Script
Step 1 — All the necessary packages are included at the beginning of the code. In this MSTest tutorial for Selenium; the following packages are included for automated web testing with Selenium C#:
- MSTest framework (Microsoft.VisualStudio.TestTools.UnitTesting)
- Selenium (OpenQA.Selenium)
- Chrome WebDriver (OpenQA.Selenium.Chrome)
Step 2 — The [TestClass] attribute in MSTest represents the class containing the unit tests. In this example, MS_Test_Cross_Browser_Test() is the class containing all the tests.
Step 3 — The [TestMethod] attribute in MSTest indicates a method that contains the test method. In this example, the test method is NavigateToDoApp() and the same is under the [TestMethod] attribute.
Step 4 — The IWebDriver interface is used for enabling browser interactions. Hence, we create an instance of the IWebDriver interface in the code. A new instance of Chrome browser is initiated using the command driver = new ChromeDriver().
The URL is set to https://lambdatest.github.io/sample-todo-app/ and the browser window is maximized using the command driver.Manage().Window.Maximize() for this MSTest tutorial for automated web testing with Selenium C#.
Step 4 — Once the Chrome browser is initiated and the target URL is loaded, we locate the required elements on the web page for automated web testing with Selenium C#. The details of the required Web Elements are obtained using the Inspect Tool in the Chrome Browser. As seen in the screenshot below for cross-browser testing, the element with Name “li1” is located using the tool.
The same approach is followed for locating the other web elements having Name - li2, li3. The other elements are located using the Id of those elements.
The FindElement command in Selenium is used along with the appropriate web locators to identify the web element. Once the web element is identified (or located), appropriate action i.e. Click, SendKeys, etc. is performed on the web element.
Step 5 — A new item (Yey, Let's add it to list) is added to the list. An assert is raised if the text in the newly added element does not match with the expected text.
The Quit WebDriver command (driver.Quit) is called once the test is complete so that the WebDriver session is closed properly and resources used by the WebDriver are freed in this MSTest tutorial for Selenium automation.
Executing The MSTest Script
To execute the newly created test (NavigateToDoApp), go to Test and press Run All Tests.
The execution progress can be seen in the Test Explorer window which can be seen by going to menu-item View -> Test Explorer.
Shown below is an execution snapshot from Visual Studio. The Green tick mark indicates that the test execution completed successfully.
Shown below is the automated browser testing execution in action in the Chrome web browser:
All In All
In this MSTest tutorial for Selenium, I took a deep-dive into automated web testing with Selenium C# using the MSTest framework to run your first MSTest Script for Selenium test automation. Interactions with the elements on the web-page were performed by using the relevant Selenium APIs. The code implementation used in this article can be scaled to execute complex Selenium test automation scenarios using Selenium C# with the MSTest framework.
This concludes this MSTest tutorial for Selenium to run your first MSTest script for Selenium test automation. I hope you found this article informative! Do share this article with your peers and colleagues looking to learn about Selenium test automation using MSTests. A retweet and share on LinkedIn are always welcome with open arms. That’s all for now. Happy Testing!
Published at DZone with permission of Himanshu Sheth . See the original article here.
Opinions expressed by DZone contributors are their own.