4. Implement Test Steps With TestLeft

Before implementing test steps with TestLeft, you need to import the required classes:

You must create an instance of the Driver class as you do this in a regular TestLeft test. The way you do this depends on your test. In our case, we create it in the first test step:

We use the LocalDriver class. This way we access the TestLeft test engine on the local computer. To access the TestLeft test engine running on a remote computer, use the RemoteDriver class.

1. Use the created driver object to run the tested application:

   C#

   C#

   [Given(@"I open Notepad")]
   public void GivenIOpenNotepad()
   {
       IDriver driver = new SmartBear.TestLeft.LocalDriver();
       IProcess notepadProcess = driver.Applications.Run("notepad.exe");
   }

   To learn more, see Running Applications From Tests.

When you create a test with TestLeft, you can inspect applications objects, their methods and properties by using TestLeft UI Spy and generate code to get them from the test.

1. Run the Notepad application.

2. In Visual Studio, select View > TestLeft UI Spy to open TestLeft UI Spy.

3. Configure the TestLeft UI Spy code generation settings. Click on the main toolbar and specify the following settings:

   • In the Languages section, select C#.

   • In The first object section, select Main form / Page. The Process variable name box should specify the name of the variable that contains a reference to the testing process. In our case, it is notepadProcess.

   

   Click the image to enlarge it.

   Click OK.

4. Hold the left mouse on the Pick Object button (the mouse cursor will turn into the target icon (). Drug the cursor to the Notepad window and drop it once a red frame appears around the edit box:

   

   Click the image to enlarge it.

   TestLeft UI Spy will select the object in the object tree. The panel on the right shows the methods and properties of the selected object:

   

   Click the image to enlarge it.

5. To verify that the Notepad window contains no text, use the wText property. Right-click the wText property and select Copy Member Call from the context menu:

   

   Click the image to enlarge it.

   TestLeft will copy the needed code to the clipboard.

6. Paste the code to the method of the next test step:

   C#

   C#

   [Given(@"there is no text in Notepad")]
   public void GivenThereIsNoTextInNotepad()
   {
       ITextEdit edit = notepadProcess.Find<ITopLevelWindow>(new WindowPattern()
       {
           WndClass = "Notepad"
       }).Find<ITextEdit>(new WindowPattern()
       {
           WndClass = "Edit"
       });
   
       string wTextValue = edit.wText;
   }

7. In this code, Visual Studio cannot resolve the notepadProcess variable. To fix that, you need to declare the corresponding variable within the class scope:

   C#

   C#

   public class RunTheUndoCommandUsingHotkeysSteps
   {
   
       // Declare the variable
       private IProcess notepadProcess;
   
       [Given(@"I open Notepad")]
       public void GivenIOpenNotepad()
       {
           IDriver driver = new SmartBear.TestLeft.LocalDriver();
   
           // Assign the object of the Notepad process to the notepadProcess variable
           notepadProcess = driver.Applications.Run("notepad.exe");
       }
   ...
   }

8. Use the Assert.AreEqual method to verify that the property contains an empty string:

   C#

   C#

   [Given(@"there is no text in Notepad")]
   public void GivenThereIsNoTextInNotepad()
   {
       ITextEdit edit = notepadProcess.Find<ITopLevelWindow>(new WindowPattern()
       {
           WndClass = "Notepad"
       }).Find<ITextEdit>(new WindowPattern()
       {
           WndClass = "Edit"
       });
   
       string wTextValue = edit.wText;
   
       Assert.AreEqual("", wTextValue);
   }

1. To implement the next test steps, you need to interact with the edit box. Therefore, you need to make it visible for other methods. Declare the corresponding variable at the beginning of the class:

   C#

   C#

   public class RunTheUndoCommandUsingHotkeysSteps
   {
       private IProcess notepadProcess;
       private ITextEdit edit;
   
       ...
   
       [Given(@"there is no text in Notepad")]
       public void GivenThereIsNoTextInNotepad()
       {
           edit = notepadProcess.Find<ITopLevelWindow>(new WindowPattern()
           {
               WndClass = "Notepad"
           }).Find<ITextEdit>(new WindowPattern()
           {
               WndClass = "Edit"
           });
   
           string wTextValue = edit.wText;
   
           Assert.AreEqual("", wTextValue);
       }
   }

2. On the next test step, you need to enter text in the Notepad window. Visual Studio’s IntelliSense shows a list of methods available to the object:

   

   Click the image to enlarge it.

   To simulate typing text, we will use the Keys method:

   C#

   C#

   [When(@"I type ""(.*)""")]
   public void WhenIType(string p0)
   {
       edit.Keys(p0);
   }

   Note that the created method contains the p0 argument. SpecFlow extracts the phrase in quotes from the text of the test step by using a regular expression and passes it to the argument.

3. To simulate pressing hotkeys, we also use the Keys method:

   C#

   C#

   [When(@"I press \[Ctrl \+ z]")]
   public void WhenIPressCtrlZ()
   {
       edit.Keys("^z");
   }

4. Finally, we check that Notepad does not contain any text. Use the Assert.AreEqual method, as we did it earlier:

   C#

   C#

   [Then(@"I should see no text in Notepad")]
   public void ThenIShouldSeeNoTextInNotepad()
   {
       Assert.AreEqual("", edit.wText);
   }

In our example, the Notepad application is still running after the test run is over. It means that when another scenario starts, it will run another instance of the application. This may cause errors and performance issues. To fix that, you must close the application when the scenario finishes. To do that, use the After attribute. SpecFlow will run a method with this attribute at the end of each test scenario. Add the following method to the test class:

The final test code is as follows: