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
When you run the testing suite, the system will first check the .xtract/containers folder for the name of all 'configured' containers, and if one is missing, then we grab it via Globus from Petrel. So a user might execute the following commands:
xtract fetch-containers [library]
where [library] can be standard, materials, or all.
Users should also then be able to run Xtract tests locally for all containers present. xtract run-tests [library]
and it will run all the tests for all of that kind of container.
The text was updated successfully, but these errors were encountered:
When you run the testing suite, the system will first check the .xtract/containers folder for the name of all 'configured' containers, and if one is missing, then we grab it via Globus from Petrel. So a user might execute the following commands:
xtract fetch-containers [library]
where
[library]
can bestandard
,materials
, orall
.Users should also then be able to run Xtract tests locally for all containers present.
xtract run-tests [library]
and it will run all the tests for all of that kind of container.
The text was updated successfully, but these errors were encountered: