We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Having a TestRunId of "v1.2" and a TestRunName of "v1.2.a1b2bc3d" is great, but what if you have two different projects with the same ID/Name?
TestRunId
TestRunName
Such as, having tests run for the core project and the website project in the same version?
This is to add a new TestRunProject identifier, which could be set to anything like "core/site/console/gui/etc.".
TestRunProject
This value will only be passed on the initial "test run has started" callout.
This value can be set on CLI or Edisonfile.
The text was updated successfully, but these errors were encountered:
Due to the re-architecture of the callouts, the TestRunProject identifier will just be passed on every call.
Sorry, something went wrong.
The TestRunProject value is optional, and can be null.
CLI: --tproj Edisonfile: test_run_project
--tproj
test_run_project
Resolves #65: Need a new TestRunProject identifier
96f6b78
Merged into Epic branch
No branches or pull requests
Having a
TestRunId
of "v1.2" and aTestRunName
of "v1.2.a1b2bc3d" is great, but what if you have two different projects with the same ID/Name?Such as, having tests run for the core project and the website project in the same version?
This is to add a new
TestRunProject
identifier, which could be set to anything like "core/site/console/gui/etc.".This value will only be passed on the initial "test run has started" callout.
This value can be set on CLI or Edisonfile.
The text was updated successfully, but these errors were encountered: