TestLink et tests de régression

L'outil est actuellement mis en place à cette adresse: https://www.ryxeo.com/testlink/. Malheureusement il n'est pas encore compatible OpenID mais on y travaille … en attendant il faudra se créer une fois de plus, des comptes utilisateurs !

Ci-dessous quelques bouts de documentation issus du manuel de l'utilisateur:

Example of TestLink simple work-flow

1. Administrator creates a Test Project “Fast Food” and two users, Adam with rights

  “Leader” and Bela with rights “Senior Tester”.

2. Leader Adam imports Software Requirements and for part of these requirements

  generates empty Test Cases. He reorganize them into two Test Suites: “Fish” and
  “Chips”.

3. Tester Bela describes a test scenario (create a content of empty Test Cases) using

  these Test Specification that is organized into Test Suites.

4. Adam creates keyword “Regression testing” and assigns this keyword to ten of these

  Test Cases.

5. Adam creates a Test Plan “Fish & Chips 1”, Build “Fish 0.1” and links all Test Cases in

  Test Suite “Fish” to this Test Plan. He assigns himself and Bela as resources to this Test
  Plan too.

6. Now developers produce a first build. Adam and Bela execute and record the testing

  with the result: 5 passed, 1 failed and 4 are blocked.

7. Developers make a new Build “Fish 0.2” and Bela tests the failed and blocked Test

  Cases only. This time these all blocked and failed Test Cases passed. They retest also
  all Test Cases with keywords “Regression testing” in addition.

8. A manager of this team would like to see the results. Administrator explains to him

  that he can create an account      himself on the login page. Manager does it. He has
  default “Guest” rights and can     see Test Results and Test Cases. He can see that
  everything passed in the overall   report ;-) and problems in Build “Fish 0.1” in a report
  for that particular Build.1

9. Later, developers finally add also “Chips” functionality. Adam creates a Test Plan “Fish

  & Chips 2”. He can reuse the first Test Plan as template. All “Fish” Test Cases and roles
  will be automatically added. He create a new Build “Fish 1.1” and links all “Chips” Test
  Cases to this Test Plan too.

10. Now testing starts as usual. 11. Later, Admin creates a new Test Project for another product “Hot Dog”. But this is

  another test team and a different story.