Testhub is an easy way to aggregate and analyze test results.
There is no need in creating account or registering. All you need is to use one of the integration methods to start uploading test results.
Please refer to our examples to check how it looks like: https://test-hub.io/testhub-io-examples
⛔ Testhub makes test results available publicly. If you don’t want to share this information please contact us.
Add our Github action: https://github.com/marketplace/actions/test-results-uploader-to-test-hub-io and specify
test_result_pattern: "/target/surefire-reports/**/*.xml"
test_coverage_pattern: "/target/site/jacoco/jacoco.xml"
Results will be available under https://test-hub.io/[GITHUB_ORGANISATION]
url
Quick start with Circle CI and Testhub Quick start Video
Example of .travis.yml
Add testhub upload step to your build process.
Install (Linux):
curl https://github.com/testhub-io/testhub-cli/releases/download/v0.13b/testhub-cli_v0.13b_linux_386.tar.gz --output testhub-cli.tar.gz -L && tar -xzf testhub-cli.tar.gz
./testhub-cli upload -t [API_TOKEN] --build $BUILD_NAME --project $ORG/$PROJECT_NAME --pattern $GLOB_PATTERN_FOR_TEST_FILES
$BUILD_NAME
- test run name or build name. Usually a build number$ORG
- organisation name, all test results will be available under this organisation name$PROJECT_NAME
- project name, usually it’s is same a git repository name$GLOB_PATTERN_FOR_TEST_FILES
- glob pattern to search for test files, like /target/surefire-reports/**/*.xml
.We support JUnit but it could be easily extended you can specify the root folder where cli starts search using -r
flag
Results will be available under https://test-hub.io/[ORG]
If you build system support using docker images you can use our pre-build image
Your test results will be available