Skip to content
Update TestLink, point and click style
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


TestLink Results Importer

This program aims to save time by allowing you to update test link test execution results directly from a .csv or .xls file. This is useful for programs like serenity-bdd that create a results.csv file after test execution. More advanced users will be interested in the underlying tri-cli app that can be run programatically during a ci job.


  • Loads a TRI.jar properties file into an easy to use graphical user interface
  • Edit and save custom properties.
  • Updates your testcases in the background while you get coffee do other testing.


All you have to do to run TRI, is download the .zip file and run app.exe.

If you don't wish to use the pre-built .exe app and have python 3.x installed, the program can be run by navigating via command line to the folder where is located, and running the command python

How to use

  1. Populate all the fields in the app then click the save button to generate a valid file.
  2. Then click the Update Testcases button and wait for the TRI tool to complete.

Frequently Asked Questions

  • How fast is it? Unscientific testing indicates that updating 1 test case status takes about 4 seconds.

  • How much time does this save? The real question, is how long does it take the average individual to update a single test case status?

  1. Enter "Username" entry
  2. Enter "Password" entry
  3. Click "Login" button
  4. Click "Test Execution" link
  5. Select "Test Plan" dropdown
  6. Select "Build" form dropdown
  7. Select "Test Case" from tree-view
  8. Click "Result" radio button
  9. Click "Save Execution" button

If each one of these steps takes 1 second, then at best a test case status can be updated in 9 seconds. In practice, this is a larger number. You can start to see where updating TestLink can become quite tedious...

Time Saved = (X*Y) - (X*Z)   |   Time Saved = (100*9) - (100*4)   |   Time Saved = (1000*9) - (1000*4)
           = (X*9) - (X*4)   |              = 900     - 400       |              = 9000     - 4000       
           = X*5             |              = 500s or 8.3 mins    |              = 5000s or 83.3 mins or 1 hour and 23.3 mins

X = Number of testcases
Y = Time to update test status manually (9s)
Z = Time to update test status using TRI (4s)

  • I found a bug, what do I do? Great, please open an issue.

  • Can I integrate this into a CI/CD build? Yes! It was designed to ease reporting on a legacy systems whose codebase is no longer being updated, but still run. If you fall into this boat, your probably going to be interested in automating this task via a CI pipeline.

  • Whats the most testcases that you have successfully updated? The most so far that anyone has told me was 1494 testcases in 1 hour and 40 minutes. Its not fast, but it works.


While the app is pretty simple, the following scenario was common enough to document. If your having trouble using the app, double check the scenario below.

Updating:1 of n --- Test Case id:12345 not found
User Associated with Developer Key has Insufficient Rights.

This error occurs when your TestLink role level access in testlink is not explicitly set. Most likely you are "inheriting" user permissions. This works for the web interface, but NOT with the API.

Steps to fix the error:

  1. Login to TestLink and navigate to the Assign User Roles Page (Top left blue link box on Home Page or Main Menu)
  2. Find your username, and check if you have the text <Inherited> before your Repository Role. If so, change it the the same access level, just without the "<Inherited>" prefix.
    NOTE: You need to do this for every Instance that you plan on using TRI with. Changing one instance's settings, does not automatically configure another one's. (If it has a different url, its a different instance)


TRI has been setup to use cx_Freeze in order to create cross platform installers. To create a executable version, navigate to the directory where the files are and run the following commands:

  • python build (Windows .exe code)
  • python bdist_msi (Windows .msi installer)
  • python bdist_dmg (Macintosh .dmg installer)



You can’t perform that action at this time.