Links

First Steps

A short, 25 minutes guide to your first test case in TestResults.io Designer.
This is a direct continuation of the First Steps with the TestResults.io portal chapter. The section below shows you how to create and publish a test case in the TestResults.io designer.
Keep in mind - this chapter only shows a brief summary of how to work with the Designer. For more details refer to the Getting started chapter

Step 1 - Download Visual Studio and TestResults.io Designer

Step 2 - Create a TestResults.io solution

  • From the Visual Studio startup screen select Create a new project, or if Visual Studio is already open select "File" --> "New" --> "Project"
  • In the Create new project dialog type in TestSolution in the search field
  • Select TestResults.io solution and press the Next button
  • Enter the Project name and press Create

Step 3 - Create an account

  • If you already have a TestResults.io account, select the Existing User button and follow the instructions on the screen
  • If you are a new user without a TestResults.io account, follow the instructions on the screen

Step 4 - Select the Project you will work with

If you have already created a Project on the Portal, you can select it here. If not create a new Project, Software version or Test case right here.
  • The Project name is usually the name of the software that you want to test. Same with the name for the Software version.
  • Name the Testcase like the process you want to test, like "Login," "User settings", "Customer Search" etc.

Step 5 - Connect to Test Environment

  • From the Extensions--> TestResults.io menu select the Test Environments tab (more information about the Test Environments can be found here)
  • Double click on the "Static Image" test environment to connect to it.

Step 6 - Add your first screen

  • Activate the Screen Editor by switching the Control Mode to "Off"
  • Enter "MyFirstScreen" as the screen name and select Screens in screen location
  • Click the arrow for the Screen loaded image and mark a rectangle around the "Static Test Image" text in the test environment.
  • Select Save Image on the right side of the Remote Viewer.
  • Click Add element and select Button.
  • Mark another rectangle around the click area (indicated by the large mouse cursor) in the Remote Viewer.
  • Enter "MyFirstButton" as the name of the selected element.
  • Click Add Buttons and then Generate Screen.

Step 7 - Modify the test case

  • In the Solution Explorer, open the class representing the test case (if your test case is "001 - My Test Case", the test case class is called "My_Test_Case.cs" in project TC001_Rev1).
  • Replace the contents of the test step 1 method as follows:
[TestStep(1,
TestInput = "First Test input",
ExpectedResults = "First Expected Result")]
public void Step1(ITester t)
{
App.MyFirstScreen.Activate();
App.MyFirstScreen.MyFirstButton.Click(App.MyFirstScreen.WaitForDisappear);
t.Report.PassStep("Click was successful");
}
  • Delete the PreconditionStep, CleanupStep and TearDown for now. Your TestCase should now look like this, with small changes depending on the name of your test case and software model:
using Progile.ATE.TestFramework;
using MySoftware_Model;
namespace TC001_Rev1
{
[TestCase(1)]
public class MyTestCase
{
private MySoftwareApp App { get; set; }
[SetupTest]
public bool Setup(ITester t)
{
App = new MySoftwareApp(t);
return true;
}
[TestStep(1,
TestInput = "TestInput1",
ExpectedResults = "Expected1")]
public void Step1(ITester t)
{
App.MyFirstScreen.Activate();
App.MyFirstScreen.MyFirstButton.Click(App.MyFirstScreen.WaitForDisappear);
t.Report.PassStep("Click was successful");
}
}
}

Step 8 - Run the test case

  • Press the F5 button
  • Observe the execution of the test case (clicking on the selected control) in the Remote Viewer

Step 9 - Publish your test case container

  • Open the Solution Explorer
  • Right click on the solution (top entry)
  • From the TestResults.io context menu select the Publish All option
Your test case has been published to the TestResults.io server and is now available for execution in the TestResults.io portal.