Subscribe Join 34,000+ subscribers and receive articles from our blog about software quality, testing, QA and security. Subscribe

Adding files to the server

A very noob question:
I’m using TestRail on cloud (, and I want to add a file to the server (as in “The trigger script (trigger.php) needs to be placed into TestRail’s installation directory on the web server”)
Problem is I can’t find a way to add any file, or see server file system. What am I missing?

Hello @zorglub76 ,

Thanks for posting. Those instructions are for the TestRail Server. However, you would also be able to use the trigger example/approach with a TestRail Cloud account.

You would simply place the server-side trigger script on the server where you would like to execute/run the tests on (usually on your private network / externally).

TestRail would not need to be able to connect to your server, as the connection/glue is made via the UI script in TestRail and via your web browser.

You can also write the server-side script in any other programming language and our script is only an example.

That said, most customers trigger their automated tests outside of TestRail either manually, scheduled or via a continuous integration system.

They then use TestRail’s API to submit the test results to TestRail.

Hey Erick,
Thanks for the reply. Just to make sure I understand this right: I can’t make UI script trigger external automated tests, because I’d need to send request to another server, and cross site scripting would not work?
My intention was to have button on TestRail page that would start a Jenkins job on another server, and then pick up results and include them in test report on TestRail. So, I’d like to have centralized tool for running both manual and automated tests, and also for reporting.
The solution would be to run Jenkins manually and have it post results to TestRail using some script that calls TestRail API?

Hi Marko,

Your logic is correct. If the trigger inside your TestRail Cloud instance is blocked due to cross-site scripting, you would need to trigger your automation job locally or directly from your Jenkins server instead.

I hope this clarifies your question,