Hello World [@Testlab]


3 minute guide to running your first test case with Testlab

So, you just registered and you want to run tests? This intro guides you to create and run your first test case.


  • your own Testlab site: for example https://yourcompany.melioratestlab.com
  • you have an user account for Testlab (with company administrator priviledges)

Register if needed here: https://www.melioratestlab.com/sign-up


Step 0: Create a project

Login to your Testlab and choose Testlab –> Manage Projects…

Click lower left-hand corner green plus-sign to create a new project.

Fill in details: for now, choose

  • name: Hello world,
  • project key: HLO and
  • Workflow: No review

See on-line manual if you want to check details of different workflows and/or fields.

Click Save to create project and then logout and login to your new project.


Step 1: Create a requirement

All test cases should be based on requirements.So we’ll define a requirement for the domain under test.

Choose view Requirements from left panel and from context menu New –> Requirement…

You can use keyboard shortcut Ctrl+N to do the same.

Enter requirement data:

  • requirement name: World should be greeted  and
  • description: As a world, I should be greeted.
  • (optionally other attributes as you see fit)

In this case, requirement summarizes in business terms what should be achieved.

Save the requirement by pressing shortcut key Ctrl+S or by clicking button Save.

Reviewing a defined requirement is an important step and normally is made as a separate phase by a client or product owner. For now, review your requirement and when satisfied, mark it ready by choosing Edit (shortcut Ctrl+E) and Mark as ready.



Step 2: Create a test case

You want to plan *how* to test your requirement. We’ll create a test case to describe exactly how we are going to test that a requirement is filled.

Choose view Test case design from left panel and use either context menu or keyboard shortcut Ctrl+Shift+N to create a new test category. Enter category name:

  • category name: human interface

Then you are ready to create a new test case. Press Ctrl+N (or context menu. again) to add test case with following data:

  • name: Listen up!
  • tab steps: Add step by choosing add step…. Enter Listen carefully and You hear hello. You can easily create more test case steps by using tab-key to move to next field in step editor.

Save test case by clicking Save (Ctrl+S). Next, review your test case and when you are satisfied, mark it ready by choosing Edit (Ctrl+E) and Mark as ready.

Choose view Test coverage to link your newly created test case to your requirement. You can do this by dragging the test case (lower left corner) to the requirement (upper left corner). Now test case is linked to the requirement. Basically this link means that requirement A should be tested with a test case B. Normally every requirement should have one or more test cases that *verify* that requirement is fulfilled correctly.

You should see immediately at the right side of the screen the effect of linking the test case to the requirement. Requirement REQ1 has now one test case (but no results yet. though. We’ll get there in 30 seconds).



Step 3: Make a test run

Choose view Execution planning from left panel and from top left, choose you personal working set Work set.

Now you can add the test case you want to execute to lower right-hand corner (labeled as test cases for test set Work set). You can do this by expanding lower left-side tree with test cases and dragging the test cases to test case list at lower right side.

You could also drag whole folders to test case list: this would add all test cases in folder to the test case list.

When you have dragged the Listen Uptest case to the list, click button Add test run…

This will open a pop-up window and create a test run with all checked test cases so that they can be executed. Enter a test run name:

  • Title: Sprint 1 run

and click Save. Now there is a new test run in upper right side with status Not started.

You could have entered also some other relevant data like expected completion date for this test run if you were planning the testing rouds well in advance.




Step 4: Run test(s)

We are ready to go: choose view Test runs, click the just created test run named Sprint 1 run from upper right side. If there were dozens of test cases, you could select a subset of test cases to run now, but we are going to select the all! Just select all test cases from lower right and click Run selected… to run selected tests.

This will open a test execution window. Each test case data will be presented to you: after clicking through test case step you have to choose either

  • Pass (test case executed successfully) or
  • Fail (test case did not run successfully)

 for test case result. Other (normally more rare) options would be

  • Blocked (test case cannot be run at the moment) or
  • Skip (skip running of test case: there is no result recorded for this test case)

If there were a problem with a test case execution and expected result was not achieved, it would be a good practice to *always* add an issue by clicking a button Add issue…

For now, just press Pass to record a successful result to your test case.

Voilà, you have completed your first test run and recorded the results to Testlab!



Bonus step (4+1)

To see where your project stands in regards to testing progress, choose again view Test coverage. Right hand side will show you the project testing status in relation to the project requirements. You should see that your single business requirement is well covered and passed all tests (=Green!).







Happy testing :)


Tags for this post: usage 

Best-of-class cross-browser hosted SaaS quality and test management, testing and issue management tools to improve your quality. Site information.