The creation and setting up of a Project would generally take just a few minutes if we are familiar with the application to be tested. This is a one-time setup and once it is done, we only need to make modifications when the application changes or new versions are released.

Basic steps involved in the creation of a project can be summarized as follows:

  1. Create a Testing Project.

  2. Add the Applications that need to be tested under the Project.

  3. After adding the Applications, we need to add the Versions that need to be tested and the Requirements for each of those Versions.

  4. We can add members to our Project Team so as to assign them roles during the addition of Test Cases.

  5. Under the Requirements, we can now start adding Test Cases that need to be executed and then add the Test Steps for each of the Test Cases.

  6. Create a Test Suite with the created Test Cases since Test Suites are mandatory for execution of Test Cases.

  7. Finally, we can add Execution to our Project for multiple Execution Environments.

Though this seems like a lot of steps, it is necessary to organize large Projects. Organization of the project in this manner helps to manage them easily when the total number of Test Cases spans to tens or hundreds.


In Testsigma, there are three levels in hierarchy of a Project that we need to know before we start. They are:

  • Applications

    • Versions

      • Requirements

Let us say that you are an E-Commerce company running an online store named ‘ECShop’(assuming your project name) and you have the following applications to manage your business online:

  1. A Web-based Customer Portal

  2. A Web-based Seller Portal

  3. An Android Web Application

  4. An Android Native Application

  5. An iOS Web Application

  6. An iOS native Application

  7. A RESTful Web Service

Also, you may have different Versions in each Application. Let us say that you have 2 Versions in your Web based Customer Portal Application, namely:

  • Version 1
  • Version 2

Along with that, you may have a set of Requirements in each Version. For example,

  1. Homepage

  2. Checkout Process

  3. Search Process

For each Requirement, we can add a number of Test Cases to test it. Test Cases contain a set of Test Steps that are performed during the execution of a particular Test Case.

Finally, our project would appear like this:



Considering the above hierarchy, we would need at least one Application and at least one Version of our application so that the Requirements can be organized below them. That is why it is highly recommended to create Application and Versions first before creating Test Cases.


  • If we don't follow versions, we may enter Default as our version name.
  • Also, if we have only one application, we may enter same for both project name and application name.