Test Runs
«Run» comes from the English Run, not from the Russian рана.
Test Run - is the execution of some test in accordance with a predefined test plan.
The plan usually states what to do and how, and which results to expect.
A run is the process/result of executing the test
step by step
, as described in the plan. After a run the outcome can be
either Accept or Fail.
Usually a test plan does not contain detailed instructions down to every single value.
That is why the tester has a certain freedom. You can enter slightly different values,
choose other menu items, apply a slightly heavier load.
The plan is the same, but the actual tests are different. Each such test is exactly a Test Run.
If the test fails during one run but not during another, it makes sense to think about making
changes to the plan, but this is by no means an axiom.
Example
Let us look at my test run from the article
«Integration Testing»
You can repeat exactly the same actions, but, for example,
choose a different city. If you take screenshots,
the design of the sites may have changed by now.
Your test run will differ from mine, but as long as
all the actions can be performed under the same plan, it
will be the same test case.
So, let us move on to the example:
Suppose you are a tester from
Aviasales
and you want to check how the integration with the site
Booking.com
works, and at the same time make sure that the hotels are visible on the map.
Here is what your test looks like in a simplified form:
| Test Case ID | Test Case Objective | Test Case Description | Expected Result |
|---|---|---|---|
| 1 | Check that the «HOTELS» button works | Go to the «Hotel search with discounts» page by clicking the «HOTELS» button on the main page | The hotel search page is shown on the site Aviasales |
| 2 | Check the interface between the aviasales.ru site and the booking.com site | Go to the site Booking.com by clicking the «Find hotels» button | The transition to the site has been made Booking.com Aviasales is listed as a partner. |
| 3 | Check the integration of Booking.com with Google Maps | Click the «On the map» button and make sure that the hotels are visible. | The map is open and the hotels can be seen on it |
Test Case ID is the test number. Test Case Objective is the goal. Test Case Description is the description. Expected Result is the expected result.
Now let us go through the actions step by step.
You need to go to the site
Aviasales
and choose some route.
Suppose you are interested in
Costa del Sol
and you want a ticket to
Malaga
,
fill in the forms and click the «Hotels» button
The transition to a new page has been made, but you are still on the same site.
You need to click the «Find hotels» button
The transition has been made, the booking site mentions Aviasales. The integration Aviasales - Booking works.
Let us check the integration Booking - Google Maps. We click the «On the map» button
The hotels are visible on the map. The integration Booking - Google Maps works.
After you have performed all the actions and written the report, you can
say that the test run is complete.
I hope it has become a little clearer to you what a test run is
Article author: Andrei Olegovich
