Tester’s Corner https://docs.microsoft.com/archive/blogs/uppadhyayraj/feed.xml In God we trust, Rest we Test! Wed, 17 Apr 2019 03:28:56 GMT en-US hourly 1 3 Steps to Automate Your Functional Tests Using Visual Studio 2015 https://docs.microsoft.com/archive/blogs/uppadhyayraj/3-steps-to-automate-your-functional-tests-using-visual-studio-2015 Sat, 10 Jun 2017 22:39:07 GMT https://blogs.msdn.microsoft.com/uppadhyayraj/?p=46 I have created a Visual Studio 2015 project template for 3 steps to automation* (after meeting the criteria). This template will help our testing team and DevOps teams for automating their functional tests and provide them flexibility to run the tests across different platforms and browsers with a simple config entry. This extension also provide capability to run the tests using Selenium or Coded UI.

Supported Platforms:

  • Windows (Mobiles devices and machines)
  • Android (Mobile devices) 

Supported Browsers and Application:

  • Chrome
  • Internet Explorer
  • UWP applications
  • Android applications

Please note overall idea of this is to create and setup automation project one single install with structure and main components without taking our code from TFS, creating your own project and setting up configuration.

Pre-Requisites:

  1. Download “Appium WebDriver” from here and install it. From the installation folder run the WinDriver.exe)
  2. Download my plug in from Market place and run it on your local machine.
  3. Download + Install OLEDB and ACE drivers for Excel.

Steps:

  1. Restart Visual Studio 2015 IDE and go for creating new project. Search for Develop_Automated_Tests template and create a new project:
  1. It will create a full project setup for you. Now open the App.config file and update following entry (TestCaseFolderFullPath) to point to your project directory (which you can get by right clicking your project name and select “Open Folder in File Explorer” option:
  1. Now build the project and resolve if there is any error. Open Test Explorer window and run any sample test as listed above, you should be able to run it. This project will have following tests and you should be able to run the tests after following these 3 steps:
  • WebTestforDesktop
  • WebTestforDesktopHeadless
  • VerifyUWPCalculatorAddFunctionality
  • For other tests we have to configure full setup for Android with Emulator (Please click here for full setup, if you want to run test for Mobile Apps)

Request you all to share:

  1. Your experience and inputs/feedback to make it better.
  2. If you face any compilation issues which are something solution need the fix, please highlight it.
]]> Producing Functional Test Automation Using Visual Studio 2015 https://docs.microsoft.com/archive/blogs/uppadhyayraj/producing-functional-test-automation-using-visual-studio-2015 Sat, 10 Jun 2017 21:50:23 GMT https://blogs.msdn.microsoft.com/uppadhyayraj/?p=45 Introduction: This post will provide you a single source for producing your test automation for your Web Application, your UWP Apps and Mobile Apps on Android by just writing 2-3 reusable lines of code. It also provides the capability of executing the tests on different platforms e.g. Windows machine, mobile devices (Windows and Android).
Targeted Audience: QA team members and DevOps team members who wanted to generate their automated tests for their regression suites and Continuous Integration in their Application life cycle.
Pre-Requites:
For TFS support:
Install Excel Providers on the machines:
Running UWP Tests:
Appium Test Running on real devices and Emulator
Pre Requisites:
Configure the environment variables in your machine:
  • JAVA_HOME: Pointing to the Java SDK folder\bin
  • ANDROID_HOME: Pointing to the Android SDK Folder.
  • Add the following paths in the Path variable: %JAVA_HOME%, %ANDROID_HOME%, %ANDROID_HOME%\tools\, %ANDROID_HOME%\platform-tools\, %JAVA_HOME%\bin\
  • Visual Studio Android Emulator: https://www.visualstudio.com/en-us/features/msft-android-emulator-vs.aspx
  • Hyper V is enabled (only for running test on Emulator)
Developing Automated Tests in Visual Studio:
  1. First download the Develop Automated UI Tests extension from Visual Studio Gallery and install it.
  2. After that go for creating a new Project in Visual Studio and select the Template "Develop UI Test Automation", provide a desired name to project and click on "Ok" button to create the project.
  3. Expends the Solution Explorer, it will show the structure as given below:
  4. It has some sample test included in the project. Expend the TestCases Folder to view the test cases, here the format for test cases is in the form of Excel file. This format is very handy business users to write their scenario which we can later convert into automated tests. Following is a typical structure of test case file, it has predefined list of Keywords, Objects are the user defined names to identify the objects, Value field contains the value to be enter on UI or to be validated on UI and Last IncludedInTestRun field specified if particular test steps need to be executed or not while running the tests:

  1. This framework stores the Objects definition in a resource file associated with the project i.e. Objects.resx file. This file has definition(s) for objects in the test case file given above by having property value of test objects for application under test. E.g. for above Objects following details of objects stored: 

  1. Once we are done with updating the Objects.resx file and creating the Test Case excel file, save the file under Test cases (or under a Subfolder) folder in the solution.
  2. Add a new unit test case class file or update existing unit test case file, create a new test method and copy paste following lines and make changes as illustrated below:

  1. Update App.config file: Make sure to update the highlighted keys according to your system:

  1. Update the Key TestCaseFolderFullPath to point to correct path:

  1. Run the tests and view the results, it provides proper results e.g. following output from a failed test case:

Result for a passed test case:

Keyword(s) Details:
Keyword
Description
Entertext
Used to provide the user values to a text box or an edit box.
+
It also contains the conditions for Username & password.
clickbutton
Used to perform a click operation on buttons or similar controls.
Ex: Clicking a Login button in login page
setpage
Used to set the page when there is change in pages during consecutive navigations. This will ensure for the easy identification of objects for the next action
+
Navigate to a page
+
Set the current page with or without title
clicklink
Used to perform a click operation on links or similar controls
Ex: Clicking on a Select link after filtering the respective role
opendropdown
Used to perform an action of opening a drop down item
selectdropdownitem
Used to perform an action of selecting a drop down item
verifydropdownitem
Used to compare the drop down items for a specific search criteria in application against to the data retrieved from database for the same search criteria
Ex: The Grade options retrieved for a specific School and School Year
openmenu
Used to perform an action on Menu items like Admin, Support etc. for providing more options for consecutive actions
verifylabel
Used to validate the content of a label
waitforprocess
Used to make the script wait for different conditions like : Wait for control ready
validategrid
Used to compare the Grid results in application against to the data retrieved from database
Ex: Student Contact Information, Student category information
clickitem
Used to perform click operation on div or similar controls
Ex: Clicking on Section Editor div
dismisswindowpopup
Used to dismiss the popup window
Ex: Clicking on “OK” or “Cancel” button
verifymessageonpopupwindow
Used to validate the message on popup window
verifyproperty
Used to validate the existence of any control
setfocus
Used to set the focus on control before performing any action
Ex: Setting focus on the button before clicking it
DragAndDrop
Used to perform drag and drop a control(with value as optional) from source location into target container
DoubleClick
Used for double-clicking a control
 Tools used for getting the properties used for find objects and running tests:
  1. For UWP app, we have to use Inspect.exe for finding the objects properties. It comes by default on Windows 8 or later and typical location for this is Program Files(x86)\Windows Kit\8.0\bin\ and then type of your system i.e. x64 or x86.
  2. For Android we can use the UIAutomatorViewer tool, which come bundled with Android SDK, once you setup the Pre requisites, you can access it just by opening up command prompt and typing uiautomatorviewer.
  3. For normal web based application in Device or on desktop we can use Dev toolbar in browsers (by pressing the F12 key) to find the objects.
Troubleshooting:
  • If getting the error on running test in Chrome then download the latest version of Chrome driver 2.28 from Google's site and copy it to following folder in Appium: \node_modules\appium\node_modules\appium-chromedriver\chromedriver\win
  • UIAutomatorViewer for getting native app's controls. Make sure devices name in Appium and Code are same and devices should have Debugging Mode enabled.
]]> Testing and Digital Transformation https://docs.microsoft.com/archive/blogs/uppadhyayraj/testing-and-digital-transformation Sat, 10 Jun 2017 21:41:43 GMT https://blogs.msdn.microsoft.com/uppadhyayraj/?p=35 Digital Transformation Scenario As the world moves on from relying on paper to cloud storage, physical stores to online store, from physically connection to becoming wireless because of constant changes in technology and competition, businesses are eventually forced to undergo a digital transformation to stay relevant in a dynamic marketplace. Any organization is going to consume a lot of time and resources whilst undergoing a transformation, but the sacrifices made are absolutely crucial to secure customer retention in the long run. We are living in the “Era of SMACT” and our lives are highly impacted by Social, Mobile, Analytics, Cloud and the Internet of Things. Every business is around these five basic technologies. Customers are changing their behavior in response and companies are keen to find out how they need to transform to survive this change. Many companies, irrespective of the industry, are facing the same challenges – how to stay on top of these new technologies and how to respond to the changing needs of the customers. Organizations are radically altering their business processes and operating models. They do this to assure superior Customer Experience. They realize that to achieve this, large-scale transformation programs are necessary. At present, organizations are investing a lot of money in implementing such Digital Transformation programs.

Is it a good idea to invest in testing during Digital Transformation?

Currently we are living an Era of Digital world and Organization are investing significantly in transforming their business/processes in the Digital world. Now, the question arises: At the end of the day, do these Digital Transformation programs lead to the expected results? In fact, to realize the desired outcomes, it’s very important find a way to detect the issues that cause unexpected results, as early as possible, in the Life-Cycle and in the Transformation journey. Quality Assurance and Testing is the answer to predict and decide the actual outcome of a Digital Transformation.  

Key Challenges in Digital Transformation and How testing provide a solution:

Every change brings associated inherited challenges which makes hard for successfully adopt the change and for be successful organization/one must find a way to overcome those challenges. Similarly, Digital Transformation also come with some key challenges. Following is the list of key challenges which organization faces while transforming their business along with facts that why should organization invest in a Quality Assurance:  

Digital is Complex:

The most difficult challenge comes from the complexities arising from the nexus of forces – Social-Mobile-Analytics-Cloud, to ensure that they work in synchronization with organizational goals. Adapting to new and latest technologies demands higher process maturity. In this scenario, Quality Assurance becomes an important function for organizations who are effectively embracing the digital transformation and they help here by come up with best processes, tools and techniques to test the complexity of the system.

Digital makes an organization vulnerable to Security Threats:

Security is of paramount importance specifically in an interconnected world. The smart interconnected ecosystems on one side enable an unimaginable world of possibilities, but it makes the entire system highly vulnerable to security threats, if not properly configured and tested, on the flip side. Testing team proactively test the vulnerability, security gap in the system at very early stage hence helping teams to address these issues simultaneously.  

Digital needs to leverage your Legacy Infrastructure:

This is again next important challenge specifically with those enterprises who are not born Digital. They need to change their organizational DNA both from a cultural perspective and from legacy IT infrastructure standpoint. Testing ensures their core functionalities are not impacted as they chart their path towards Digital Infrastructure can be much challenging.

Digital can make or break your Customer Experience:

Delivering enhanced customer experience while leveraging a variety of components of Digital Ecosystem becomes challenging. Ensuring each component delivers optimum performance leading to customer delight becomes difficult as an organization becomes more digitally matured. Changes in customer behavior, elevated global competition, adoption of social media channels and emerging trends such as cloud and mobile are a few market driven challenges that organizations must deal with during their digital transformation journey. Quality Assurance/ Testing plays a crucial role in responding to these challenges. It’s essential for organizations that are dealing with digital transformation to have an appropriate digital assurance strategy, with the right tools, methodologies and measures to assure customer experience.  

Digital demands Agility:

In Digital Transformation world, applications are expected to be delivered quicker than ever. None has the time to wait for the long-term release cycles. It is regarded as the thrusting force for agile and DevOps based delivery processes. Being Agile through continuous quality assurance initiatives, and automating processes to ensure shorter delivery cycles become highly critical in a highly dynamic digital landscape.  

Getting a true state of Development:

Inherited aspect of Testing is, its Test Report. Test Reporting provide a good way to help stake holder to provide the actual health of the system by providing a test reporting, which covers following aspects and help them to proactively make key decisions:  
  • Quality of the product/component(s).
  • Provide a holistic view of performance
  • Assess - Vulnerability, reliability and availability.
  • Bottlenecks in the system.
  • Trends across different components in the system.

Conclusion:

Quality Assurance & Testing is crucial and plays a critical role in any digital transformation journey. It’s essential for organizations that are dealing with a digital transformation to have an appropriate digital assurance strategy by identifying the right tools, methodologies and measures to assure customer experience and make the organization future ready.]]> SharePoint Test Automation using CSOM (Client Side Object Model) https://docs.microsoft.com/archive/blogs/uppadhyayraj/sharepoint-testautomation-usingcsom Mon, 22 May 2017 08:50:36 GMT https://blogs.msdn.microsoft.com/uppadhyayraj/?p=1 Abstract: Testing of SharePoint applications including unit testing is one of the popular topic of debates. This puts more onus on the QA/Test teams to test SharePoint applications even more extensively. You can of course automate SharePoint’s GUI using Visual Studio Coded UI tests, which has an excellent support for SharePoint. Automating SharePoint’s GUI is not very different from automating any other web application, where user actions and interactions are recorded and played back. This is a good approach for functional testing or black box testing but we are really not focusing on SharePoint related components in this case. In this article, we would like to propose an alternative approach that can be much more effective when you are specifically interested in testing SharePoint components without over relying on end-to-end GUI testing, which can be fragile due to high maintenance effort and generally happens too late in the game. APIs based automation is also much faster than running GUI based automation tests The suggested approach is to leverage SharePoint Client Side Object Model (CSOM) API’s and our CSOM add-in published on Visual Studio Gallery to help improve SharePoint test coverage. The add-in supports SharePoint 2010, SharePoint 2013 and Microsoft SharePoint Online. The advantage of using approach is that this code doesn’t need to run on SharePoint server and it is executed from any client machine, provided the user has the required permissions on the SharePoint site under test. This approach would help the development and test teams in improving the quality of code and minimize SharePoint related deployment and configurations issues, which are major pain points today. This can also be very handy in validating content and features in SharePoint upgrade and migration scenarios. Testers can write test-cases even no application is available, if proper design document is available then that can be refer. We will provide a walk-through of this approach and how QA/Test teams can use or extend it to automate their SharePoint test scenarios.
  • You can directly write your automated test by writing managed code to interact with SharePoint CSOM API’s but or leverage our CSOM add-in that consists of common libraries that are built on top of SharePoint CSOM API’s to accelerate SharePoint automated testing. These helper methods address generic SharePoint test requirements, which we have derived from our learning of executing SharePoint test engagements, with the intent to verify various properties and attributes of SharePoint objects.
  • You will also learn the other benefits of using SharePoint CSOM APIs for test activities like test data generation, build verification testing and deployment testing
Pre-Requisites It is assumed that the audience will have basic knowledge of following tools and concepts for using this approach
  • Visual Studio 2012/2013/2015, C#.Net, Unit Tests
  • SharePoint 2010/2013/2016/SharePoint Online
Overview of SharePoint test requirements
  • List items/Schema Validations like column its type and other properties of lists.
  • Library items/Schema Validations like column its type and other properties of library.
  • Site columns and its properties like its type, is it required filed or not, validation, default values etc.
  • Content types and its columns validation.
  • User groups, users and permission validations.
  • Site hierarchy, Web parts and Pages validations.
  • Test data generation for SharePoint objects like List, Libraries etc.
  Using SharePoint CSOM’s Visual Studio Add-in to test SharePoint applications:
  • Download our CSOM Add-in or Go to Visual Studio IDE  -> Tools -> Extension and search for “SharePoint Test Automation” Create a Test Project in Visual Studio 2010/2013
  • Add reference to all DLLs downloaded from the add-in to the test project.
  • Add Name Space for SharePoint Client API and Test Automation Framework
  • using System; using System.Text; using System.Collections.Generic; using System.Linq; using Microsoft.VisualStudio.TestTools.UnitTesting; //Name Space for SharePoint Client API using Microsoft.SharePoint.Client; //Name Space for Framework using Test.Automation.SharePointCOM.Verification;
  • Use the framework classes and initialize the SharePoint Application Under test: //Adding Reference to the class which have verification method
SPVerification verifySite; String TestSite, Domain, UserName, Password;     //Function for setting up the SharePoint Site under Test [TestInitialize] public void SetUp() { TestSite = "https://SharePointWebApp/sites/SiteCollection/TestSite"; Domain = "MyDomain"; UserName = "SiteAdmin"; Password = "Password"; verifySite = new SPVerification(); //Setting the SharePoint Site Under Test Assert.IsTrue(verifySite.SetSiteUnderTest(TestSite, UserName, Password, Domain, testContextInstance)); }  
  • Add a test method in the unit test file to validate a list on a SharePoint Point site (In the framework each method return a true or false which should be used with asserts to check the pass or fail status of a test) /*Test Method to Verify the Expected list on a SharePoint Site mentioned in the SetUp (In test initialization method)*/ [DataSource("Microsoft.VisualStudio.TestTools.DataSource.CSV", "C:\\TestData\\TestSite\\SP-Lists.csv", "SP-Lists#csv", DataAccessMethod.Sequential), TestMethod]
public void VerifySPLists() { string ListName = testContextInstance.DataRow[0].ToString(); Assert.IsTrue(verifySite.VerifyLibraryExists(ListName, testContextInstance)); }
  • Run the test
  • Analyze the result (Framework uses the Test Context to log the results, which is useful to log the bugs and understand where the issue is):
[caption id="attachment_25" align="alignnone" width="624"]Execution Results Execution Results[/caption]]]>