Hello Steve,

sorry for the late response. We definitely plan to begin the work on a basic API soon. There's currently no concrete date for this but we expect to begin the work on an API (and also add support for automated tests) after our current roadmap is implemented:

http://blog.gurock.com/postings/testrai … 1-q2/1157/

The next release (scheduled for this week) will include support for custom fields. After we've added support for Unicode and changed the test case history behavior, we plan to work on automated tests and the API.

I hope that makes our plans a bit clearer.

When you change the status of a test (status_id of the tests table), TestRail also re-calculates and updates the stats of the parent test run (and also the parent test plan, if available). It's probably too time-consuming to re-implement the whole functionality yourself (and it may require changes for future TestRail updates).

While TestRail uses Javascript and Ajax to implement the test dialog and submitting the test result, it's actually a normal HTTP POST request. TestRail just sends a POST request to:

/index.php?/tests/ajax_add_change

Arguments are passed as JSON encoded array. There are few additional details you would need to know in case you want to implement this (authentication handling, for example), just let me know in case you are interested in this option and I will prepare an example.

Regards,
Tobias

Sure, I will prepare a simple example to call the HTTP routine and either email you or post the example tomorrow. Do you have a preference for a specific platform/language? If not, I will just use cURL in a simple shell or PHP script to demonstrate this (you can use this knowledge to call the HTTP routine with basically all platforms/languages).

Regards,
Tobias

Hello Steve,

Here's the script (it's actually a bash script, not PHP, hope it's OK):

#!/bin/sh

# Definitions that must be set before using this script. Note
# that the user email and password must be URL encoded.

URL="http://<testrail>/index.php"
LOG="update_test.log"

USER_EMAIL="someone%40example.com"
USER_PASS="<password>"
USER_TOKEN="<token>"
USER_COOKIE="cookie.txt" # where to store the returned cookie

function usage()
{
  echo "Usage: $0 <test_id> <status_id>"
  exit 1
}

# Check the script arguments

if [ -z $1 ]
then
  echo 'Error: Test ID missing'
  usage
fi

if [ -z $2 ]
then
  echo 'Error: Status ID missing.'
  echo 'Please use one of the following IDs:'
  echo '1: Passed'
  echo '2: Blocked'
  echo '3: Untested'
  echo '4: Retest'
  echo '5: Failed'
  usage
fi

TEST_ID=$1
STATUS_ID=$2

# Login

curl -c $USER_COOKIE -d "email=$USER_EMAIL&password=$USER_PASS" $URL?/auth/login

# Update the test

DATA="arguments=%7b%22test_id%22%3a%22$TEST_ID%22%2c%22status_id%22%3a%22$STATUS_ID%22%2c%22_token%22%3a%22$USER_TOKEN%22%2c%22is_result%22%3atrue%7d"
curl -H "X_REQUESTED_WITH: XMLHttpRequest" -b $USER_COOKIE -d $DATA $URL?/tests/ajax_add_change >> $LOG

# And logout again

curl -c $USER_COOKIE -d "" $URL?/auth/logout
rm $USER_COOKIE

You can use it as follows:

$ sh update_test.sh <test_id> <status_id>

The URL, email and password for the user and some other options must be configured in the script itself. Note that the email and password must be URL-encoded (please see the example values above). The USER_TOKEN variable must be set to the csrf token of the user who submits the request (the value can be looked up in the 'users' database, the field is called 'csrf').

Just let me know in case you have questions.

Regards,
Tobias

Just tested and it works perfectly!  This solves 80% of our automation needs.  Thanks very much for getting this to me so quickly.