You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already employ this approach with tests added in the external group, but as we are bringing in tests to other groups where we pull from other repositories, there needs to be proper documentation of dependencies, prereqs, and good tracking of branches/tags/SHAs that were used.
We can do this with a simple test.properties file that discloses prereqs/dependencies, that TKG can read and also add the SHAs for what instance of test material in use. TKG should also exit early if dependencies are not present on the machine where the tests are about to be run.
We already employ this approach with tests added in the external group, but as we are bringing in tests to other groups where we pull from other repositories, there needs to be proper documentation of dependencies, prereqs, and good tracking of branches/tags/SHAs that were used.
We can do this with a simple test.properties file that discloses prereqs/dependencies, that TKG can read and also add the SHAs for what instance of test material in use. TKG should also exit early if dependencies are not present on the machine where the tests are about to be run.
Related:
#5134 (comment)
Also will help enable:
#5142
The text was updated successfully, but these errors were encountered: