​TestProject plugin for TeamCity provides an easy way to execute TestProject jobs, update applications, data sources, project parameter, test packages and generate configuration for the TestProject Agent.
Prerequisites
In order to use this plugin you need to have: 1. An active TestProject account which can be created for free at https://testproject.io. 2. At least one registered and running TestProject Agent.
How to use
Install the plugin in your TeamCity server.
Go to 'Administration' > 'Integrations' > 'TestProject' > set your TestProject API key (which can be obtained here).
Create a new build step and select 'TestProject' in the 'Runner type' dropdown.
Now, simply select the action that you want to perform in TestProject.
Here's how you can get the ID of your project, job, agent, etc:
Project id:
Copy ID
Job id:
Copy ID
Test package id:
Copy ID
Project parameter id:
Copy ID
Agent id:
Copy ID
Data source id:
Copy ID
Application id:
Copy ID
Build Steps
Running a TestProject Job
Using this step, you can trigger TestProject jobs as part of your TeamCity test build. To trigger a job, you need to provide the following parameters:
Project Id - The ID of the project containing the job.
Job Id - The ID of the job to execute.
Agent Id(optional) - The ID of the TestProject agent that will execute the job. Leave this field empty to use the default agent defined for this job.
Wait to finish - How many seconds should the step wait for the automation job to finish. If 0 is provided, the setup will not wait for the job to finish execution.
Path to the JUnit XML report(optional) - Path (including the file name) to a file where the JUnit XML report will be stored. The file path can be absolute or relative to your workspace.
Execution Parameters(optional) - A JSON object that allows you to override the job's default settings and parameters for a single execution. Here's an example:
1
{
2
"browsers":[
3
"Chrome"
4
],
5
"devices":[
6
"AAA111BBB"
7
],
8
"queue":true,
9
"restartDriver":true,
10
"projectParameters":{
11
"ProjectParameter1":"Value1",
12
"ProjectParameter2":"Value2",
13
"ProjectParameter3":"Value3"
14
},
15
"testParameters":[
16
{
17
"testId":"string",
18
"testPosition":0,
19
"dataSourceId":"string",
20
"reinstallApp":true,
21
"data":[
22
{
23
"TestParameter1":"Value1",
24
"TestParameter2":"Value2",
25
"TestParameter3":"Value3"
26
}
27
]
28
}
29
]
30
}
Copied!
Please visit our API documentation to read more about using execution parameters when running a job.
Example
Copy ID
Updating a Mobile Application (apk/ipa) File
Using this step, you can update an existing Android or iOS application file as part of your build.
The step accepts the following parameters:
Project Id - The ID of the project containing the application.
Application Id - The ID of the application to update.
Path to the .apk/.ipa File - The path to apk/ipa file. The file path can be absolute or relative to your workspace.
Example
Copy ID
Updating a Web Application URL
Using this step, you can update the URL of a web application.
The step accepts the following parameters:
Project Id - The ID of the project containing the application.
Application Id - The ID of the application to update.
Application URL - The new URL address.
Example
Copy ID
Updating a Data Source
Using this step, you can update an existing data source file (.csv).
This step accepts the following parameters:
Project Id - The ID of the project containing the data source.
Data Source Id - The ID of the data source to update.
Path to the .csv File - The path to the data source (.csv) file. The file path can be absolute or relative to your workspace.
Example
Copy ID
Updating a Project Parameter
Using this step, you can update the value of any project parameter in your project.
The step accepts the following parameters:
Project Id - The ID of the project containing the parameter.
Parameter Id - The ID of the parameter to update.
Value - The new value that should be assigned to the parameter.
Example
Copy ID
Updating a Test Package
Using this step, you can update an existing test package (coded test) in your project.
The step accepts the following parameters:
Project Id - The ID of the project containing the test package.
Test Package Id - The ID of the test package to update.
Path to the .jar/.dll/.zip File - The path to the new test package file (.jar/.dll/.zip). The file path can be absolute or relative to your workspace.
Resolve Conflicts [true/false] - Should TestProject try to automatically resolve conflicts?
A conflict may arise if the updated test package is used by other tests or the new packages contains breaking changes such as removed test cases, etc.
Example
Copy ID
Generating TestProject Agent Configuration
Using this step, you can generate configuration for a TestProject Agent.
This can be used to allow a TestProject Agent running in a docker container to automatically register, execute a job and terminate on completion.
This step accepts the following parameters:
Job Id(optional) - The ID of the job to execute.
Agent Alias(optional) - An alias (name) for the agent.
This parameter is optional. If no value is provided, TestProject will generate an alias for you.
Temp Agent(optional) - A temp agent will be deleted from the account once it shuts down.
Execution Parameters(optional) - A JSON object containing job execution parameters.
This parameter is optional. If no value is provided, the job will be executed with its default configuration.
1
{
2
"browsers":[
3
"ChromeHeadless",
4
"FirefoxHeadless"
5
]
6
}
Copied!
The agent configuration will be stored automatically in your workspace. You can find the full path in the build logs.
You can also save the agent configuration token in an environment variable and use it later whenever you need. To store it in an environment variable, create new parameter (it should be of type 'Environment Variable') in your build and name it env.AGENT_CONFIG.
Please visit our docker hub page to read more about TestProject Agents containers