Monday, 10 August 2015

Limit TestMethod Timeout in CodedUI

Sometimes when we have Test Methods which run for long time, we tend to see the below kind of exceptions and TestMethod execution stops.
"Test 'TestMethod_Name' exceeded execution timeout period." 
By default Execution time for a test method is 60mins.
This test execution timeout can be changed as per our requirements.
It can be either changed in the Settings file or else

First way is to Set a limit time for execution which is as shown below
public void TestMethodName()

Second is to set infinite time limit when we dont know how much time the execution is going to happen or if we are expecting the execution to run completely irrespective of the time

public void TestMethodName()

Wednesday, 29 July 2015

Execute CodedUI TestMethod() through command prompt

Input the path of the dll in the Developer Command Prompt for VS2012/13..
cd C:\Users\...\Documents\Visual Studio 2012\Projects\CodedUITestProject\CodedUITestProject\bin\Debug
Using VSTest.Console.exe like this:
VSTest.Console.exe CodedUITestProject.dll /Tests:TestMethod1,testMethod2 /UseVsixExtensions:true  /Logger:trx
Note There is no /resultsfile option in VSTest.Console.exe command line. You need to use /Logger.trx if you want to generate a trx file.

Note The /Tests command line option cannot be used with the /TestCaseFilter command line option.

Usage  of /TestCaseFilter
Examples of /TestCaseFilter usage with filter as Priority

Examples of /TestCaseFilter usage with filter as Test Category

Examples of /TestCaseFilter usage with multiple filters using "|"

Monday, 20 July 2015

Schedule Coded UI Test to Execute At a Specific Time

The best way I have found to accomplish this is to create a .bat file which executes the test using the mstest command line tool, and setting this .bat to execute at a specific time using task scheduler. I currently do this daily on a project I am working on.
Here are the steps oulined to execute a .bat driven Coded UI test at a specified time.

Create a .bat similar to the following:
set mstestPath="C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE"
 %mstestpath%\mstest /testcontainer:AutomatedUITest.dll  /resultsfile:TestOutput.trx
Test your script by double-clicking the .bat and assure that the test is properly executing.

Assuming you name this .bat “TestRunner.bat”, you would then open Task Scheduler (pre-installed on Windows, type “Task” into the search bar to locate). You will see Task Scheduler (local) in the upper left of the window. Right-click, then select create Task. Give the task a name and choose appropriate security settings. Click the Triggers tab, and assign when you wish the test to auto-execute. In this screen you can set the appropriate time to run. Now click the Actions tab, click new and assign your script “TestRunner.bat” to execute and any parameters you may wish to feed to your script. Now choose settings and allow the test to run on demand. Ensure your test is executing properly by clicking the Task Scheduler Library underneath Task Scheduler (local), locate your task, right-click and choose run. If everything executes as expected, you can rest assured that your scheduled task will properly execute at the time(s) you have designated.

Monday, 15 June 2015

Invoking a TestMethod from TestCleanUp in CodedUI

While running a Test method, suppose the application went down suddenly or a time out issue came up because of which ContolNotFound exception occurred and got existed from the test method.
In this scenario in order to invoke the test method from the TestCleanup again this is how we do

 public override void MyTestCleanup()
      // Here i am writing for an generic flow checking my test failed.
      // you can check if any time out window availability or application down messages in browser
      if (TestContext.CurrentTestOutcome == UnitTestOutcome.Failed)
            var type = Type.GetType(TestContext.FullyQualifiedTestClassName);      
            if (type != null)
                var instance = Activator.CreateInstance(type);
                var method = type.GetMethod(TestContext.TestName);
                    method.Invoke(instance, null);

Tuesday, 2 June 2015

selenium Webdriver script with SpecFlow and Visual Studio

SpecFlow is the .Net version of Cucumber. This is a Behavior development framework for .Net. Here we will show how we can implement our Selenium Webdriver script using SpecFlow framework.

Test Case : Verify the search Functionality of Google Search page
  • Open the browser and navigate to “”.
  • Enter the word “SpecFlow” as Search Text.
  • Click on Search button.
  • Verify the search result.

Step One : Installing IDE integration package for SpecFlow 
  • Open Visual Studio and go to Tools>>Extension and Updates…
  • Extensions and Update window is displayed. Enter the word “SpecFlow” at search text box and press enter from keyboard. “SpecFlow for Visual Studio 2013” package is displayed as Search Result.
  • If you see Disable and Uninstall button then it means it is already installed with your IDE like the following.

  • If you see Download button then Click on this button.

  • It starts downloading.

  • After finishing download,click on Install button.

  • After finishing installation, click on Restart Now button.

  • Visual Studio will be restarted and if you go to Tools>>Extension and Updates… and search with “SpecFlow” then you see “SpecFlow for Visual Studio 2013” is installed.
  • In the same way search the extensions “NUnit Test Adapter” and Download it. It is used for NUnit Framework.

  • Click on Install button.

  • Click on Restart Now button to restart Visual Studio.

Step Two : Crating a new project with Unit Test Framework
  • Click on File menu and go File>>New>>Project

  • New project window is displayed.
  • Select Visual C#
  • Select Test
  • Select Unit Test Project

  • Enter project name as “GoogleSearchTest”
  • Select Location. In my case “D:\Development\”.
  • Select Solution name. In my case Solution name is same as Project name.
  • Check Create Directory for solution
  • Click on OK button.

  • “GoogleSearchTest” project is created.

Step Three : Add SpecFlow  reference from
  • Go to Solution Explorer and Right click on Reference and click on Manage NuGet Packages…

  • Manage NuGet Packages window is displayed.
  • Enter the text SpecFlow at search text box and press enter from Keyboard.
  • SpecFlow package is displayed at Search list.
  • Click on Install button.
  • Installation Started.
  • After finishing installation, a green color icon is displayed and shown that SpecFlow is installed.
  • In the same way, we need to add SepcFlow.NUnit package.
  • Clicking on Install button will install this package.
Step Four : Add Selenium Webdriver reference from
  • Enter the text Selenium WebDriver at search text box and press enter from Keyboard

  • Selenium WebDriver package is displayed at Search list.

  • Click on Install button.

  • Latest WebDriver will be installed and added as Reference.

  • Select Selenium WebDriver Support Classes package and click on Install button.
    • After finishing installation and click on Close button to close the Package Manager window.
    • Now verify that all the References are showing properly at the solution explorer.

    Step Five : Create a Feature file and write test case steps using gherkin syntax
    • Right click on the Project and go to Project>>Add>>New Item.
    • Add New Item window displayed.
    • Select Visual C# Items.
    • Select SpecFlow Feature File.
    • Enter file name as “GoogleSearchFeature.feature”. Note that Feature file name must have the extension “.feature”.
    • Click on Add button.

    • New Feature file is added with the project.
    • Double click on the File name “GoogleSearchFeature.feature” and File is opened at the Editor with default text.
    • Write the Feature name as “GoogleSearch”. Remove all the default text from Feature section.
    Feature: GoogleSearch
    • Write the case title as the scenario.
    Scenario: Verify the search Functionality of Google Search page
    • Write the test case steps using Gherkin syntax (Given…GoogleSearchWhen…Then).
    Given : It describes the precondition to execute test steps.
    When : It describes the steps to perform the test.
    Then : It describes the expected result. 
    In our case, Given clause will be,
    Given I navigate to the page ""
    And I see the page is loaded
    Note that we an “And” operator to write multiple clauses. 
    When clause will be,
    When I enter Search Keyword in the Search Text box
    | Keyword  |
    | SpecFlow |
    And I click on Search Button
    Note that here we write data table for search keyword where we use “Keyword” as the table column name and “SpecFlow” is the data. 
    Then clause will be,
    Then Search items shows the items related to SpecFlow
    Now the Feature file looks like, 
    Step Six : Write code for every step
    • Here we write code for every Feature file steps.
    • In Order to write code we need Add a step definition class.
    • Right click on the Project and go to Project>>Add>>New Item
    • Add New Item window is displayed.
    • Select Visual C# Items.
    • Select SpecFlow Step Definition
    • Enter file name as “GoogleSearchFeatureSteps.cs”.
    • Click on Add button.
    • New class file is added with the project named “GoogleSearchFeatureSteps.cs”.
    • Go to GoogleSearchFeature.feature file.
    • Right click on Feature name and click on Generate Step Definitions
    • Generate Step Definition Skeleton window is displayed.
    • Click on Copy Methods to clipboard button and window is closed.
    • Go to GoogleSearchFeatureSteps.cs class. Remove all the sample codes from the class and it looks like the following.

    • Right click on the editor and paste the code on GoogleSearchFeatureSteps class.GoogleSearchFeatureSteps.cs class looks like the following. 
    • Now we need to write automated scripts for every steps
    • We need to add the following name space at GoogleSearchFeatureSteps.cs class.
    • Go to GoogleSearchFeature.feature file.
    • Right click on the First line of Given clause and click Go to Step Definition.

    • Note that  GoogleSearchFeatureSteps.cs file is opened and mouse cursor is blinked on the Given method. Also note that method name is the combination of all word of Given clause.

    • Write the code for GivenINavigateToThePage() method.
    Note that we do not need to write any comment here as Methods name describes the steps. This is the contribution BDD.
    • Write code for GivenISeeThePageIsLoaded() method.

    Here we just verify that appropriate page is loaded.
    • Write code for WhenIEnterSearchKeywordInTheSearchTextBox() method.

    Note that we use list of data in our feature file that SpecFlow converts to table. We can use it as normal Row/Column concept.
    • Write code for WhenIClickOnSearchButton() method.
    • Write code for ThenSearchItemsShowsTheItemsRelatedToSpecFlow() method.

    • GoogleSearchFeatureSteps.cs class looks like the following,

    Step Seven : Run the test
    • Delete default class UnitTest1.cs as it is not needed.

    • Build the solution by going to Build>>Build Solution.
    • Go to Test>>Windows>>Test Explorer
    • Note that the scenario name is the test name VerifyTheSearchFunctionalityOfGoogleSearchPage
    • Right click on the test name and click on Run Selected test.

    • Test will run using NUnit and Passed.

    • Click on Output link.
    • We see the output step by step as it is written in our Feature file.

    This is the power of SpecFlow using BDD.
    Lot more new things are coming…

    Monday, 11 May 2015

    Creating .CAB files with Powershell

    Syntax for creating a cab file
    New-CabinetFile -Name -File "File01.exe","File02.txt"
    --This creates a new file in the current directory and adds the File01.exe and File02.txt files to it, also from the current directory.
    Syntax for extracting a cab file
    Get-ChildItem C:\CabFile\ | New-CabinetFile -Name -DestinationPath C:\Users\UserA\Documents
    --This creates a new C:\Users\UserA\Documents\ file and adds all files within the C:\CabFile\ directory into it.
    Code for the New-CabinetFile function:
    function New-CabinetFile {
            [Parameter(HelpMessage="Target .CAB file name.", Position=0, Mandatory=$true, ValueFromPipelineByPropertyName=$true)]
            [string] $Name,
            [Parameter(HelpMessage="File(s) to add to the .CAB.", Position=1, Mandatory=$true, ValueFromPipeline=$true)]
            [string[]] $File,
            [Parameter(HelpMessage="Default intput/output path.", Position=2, ValueFromPipelineByPropertyName=$true)]
            [string[]] $DestinationPath,
            [Parameter(HelpMessage="Do not overwrite any existing .cab file.")]
            [Switch] $NoClobber
        Begin { 
            ## If $DestinationPath is blank, use the current directory by default
            if ($DestinationPath -eq $null) { $DestinationPath = (Get-Location).Path; }
            Write-Verbose "New-CabinetFile using default path '$DestinationPath'.";
            Write-Verbose "Creating target cabinet file '$(Join-Path $DestinationPath $Name)'.";
            ## Test the -NoClobber switch
            if ($NoClobber) {
                ## If file already exists then throw a terminating error
                if (Test-Path -Path (Join-Path $DestinationPath $Name)) { throw "Output file '$(Join-Path $DestinationPath $Name)' already exists."; }
            ## Cab files require a directive file, see '' for more info
            $ddf = ";*** MakeCAB Directive file`r`n";
            $ddf += ";`r`n";
            $ddf += ".OPTION EXPLICIT`r`n";
            $ddf += ".Set CabinetNameTemplate=$Name`r`n";
            $ddf += ".Set DiskDirectory1=$DestinationPath`r`n";
            $ddf += ".Set MaxDiskSize=0`r`n";
            $ddf += ".Set Cabinet=on`r`n";
            $ddf += ".Set Compress=on`r`n";
            ## Redirect the auto-generated Setup.rpt and Setup.inf files to the temp directory
            $ddf += ".Set RptFileName=$(Join-Path $ENV:TEMP "setup.rpt")`r`n";
            $ddf += ".Set InfFileName=$(Join-Path $ENV:TEMP "setup.inf")`r`n";

            ## If -Verbose, echo the directive file
            if ($PSCmdlet.MyInvocation.BoundParameters["Verbose"].IsPresent) {
                foreach ($ddfLine in $ddf -split [Environment]::NewLine) {
                    Write-Verbose $ddfLine;
        Process {
             ## Enumerate all the files add to the cabinet directive file
            foreach ($fileToAdd in $File) {
                ## Test whether the file is valid as given and is not a directory
                if (Test-Path $fileToAdd -PathType Leaf) {
                    Write-Verbose """$fileToAdd""";
                    $ddf += """$fileToAdd""`r`n";
                ## If not, try joining the $File with the (default) $DestinationPath
                elseif (Test-Path (Join-Path $DestinationPath $fileToAdd) -PathType Leaf) {
                    Write-Verbose """$(Join-Path $DestinationPath $fileToAdd)""";
                    $ddf += """$(Join-Path $DestinationPath $fileToAdd)""`r`n";
                else { Write-Warning "File '$fileToAdd' is an invalid file or container object and has been ignored."; }
        End {
            $ddfFile = Join-Path $DestinationPath "$Name.ddf";
            $ddf | Out-File $ddfFile -Encoding ascii | Out-Null;
            Write-Verbose "Launching 'MakeCab /f ""$ddfFile""'.";
            $makeCab = Invoke-Expression "MakeCab /F ""$ddfFile""";
            ## If Verbose, echo the MakeCab response/output
            if ($PSCmdlet.MyInvocation.BoundParameters["Verbose"].IsPresent) {
                ## Recreate the output as Verbose output
                foreach ($line in $makeCab -split [environment]::NewLine) {
                    if ($line.Contains("ERROR:")) { throw $line; }
                    else { Write-Verbose $line; }
            ## Delete the temporary .ddf file
            Write-Verbose "Deleting the directive file '$ddfFile'.";
            Remove-Item $ddfFile;
            ## Return the newly created .CAB FileInfo object to the pipeline
            Get-Item (Join-Path $DestinationPath $Name);