Requires a GitHub account and an Online CI account (Travis CI or Circle CI).
Creating a new Connected Project consists of selecting an available GitHub repository in the new project list. Once you've added Testspace to your CI, test results and other metrics are automatically collected for each and every branch on all jobs.
The below example demonstrates how Testspace supports the
GitHub branch workflow. The example
published results can be viewed Here.
The following steps will guide your setup requirements:
new Repoto Travis CI (requires
resync) or Circle CI (
don't build yet)
New Project(see below)
Update yaml Filefor CI system (see below)
Push Branchto remote GitHub Repo (see below)
New Project button to bring up the dialog below.
Select the getting.started repository from the list and click
OK. A new Testspace Project will be created, connected to the repository. New Spaces, one for each active branch, will be created automatically the first time test results and other metrics are pushed from a CI system.
yaml file requires changing YOUR-subdomain to the Testspace organization subdomain selected.
Update YOUR-subdomain in the yml file.
Only the your-subdomain requires updating in the
.travis.yml for pushing results to Testspace.
before_install: - mkdir -p $HOME/bin - curl -fsSL https://testspace-client.s3.amazonaws.com/testspace-linux.tgz | tar -zxvf- -C $HOME/bin - testspace config url YOUR-subdomain.testspace.com
after_script: - testspace analysis.xml [tests]results*.xml coverage.xml
Only the your-subdomain requires updating in
circl.yml for pushing results to Testspace.
dependencies: pre: - curl -fsSL https://testspace-client.s3.amazonaws.com/testspace-linux.tgz | tar -zxvf- -C $HOME/bin - testspace config url YOUR-subdomain.testspace.com
test: post: - testspace analysis.xml [tests]results*.xml coverage.xml
Do stuff – new branches, pull request, etc. Testspace automatically tracks the branch workflow!
After the job has pushed successfully, in the Project's
Spaces tab, select the new Space which will take you to the
Schema tab where you can review the result's hierarchy and the data that was pushed. Select the
Metrics tab to review the newly created charts for test suites, test cases, acn code coverage.
For more information on How to Push Data - organize results, create folders, use incrementally uploads, include git source code changes, and other push options