Project

General

Profile

Feature #19097

Have a special name for the test suite in charge of generating reference files

Added by Gianluca Petrillo about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Low
Start date:
02/22/2018
Due date:
% Done:

100%

Estimated time:
Duration:

Description

The test suite run when asking for regeneration of reference files is seq_test_<EXPERIMENT>, which is in fact a specific sequential test.
I would like the name of that test suite to be either configurable or otherwise clearly stating its purpose.
For example, we may end up with two sequential tests, e.g. one for single muons and one for GENIE interactions, and seq_test_sbndcode would have to be defined to include both.
While this is possible, it's less than straightforward.

History

#1 Updated by Vito Di Benedetto about 3 years ago

  • Status changed from New to Assigned
  • Assignee set to Vito Di Benedetto

#2 Updated by Vito Di Benedetto about 3 years ago

  • Status changed from Assigned to Work in progress
  • % Done changed from 0 to 60

Currently the CI test suite to use to generate reference files is defined in the specific section of CI workflow configuration used to define the workflow used to update the reference files.
The better way that I see to allow the user to choose the appropriate CI test suite to generate reference files, is to add an option to the trigger script to choose the CI test suite to update reference files. The option name is "--gen-ref-tests". Maybe a better name could be used.
Then the user needs to specify an appropriate CI test suite to test the new reference files through the CI tests phase. The existing option for this purpose is "--ci-tests".
Those options are optional, as a default value can be set in the CI workflow configuration.

#3 Updated by Vito Di Benedetto about 3 years ago

  • Status changed from Work in progress to Resolved
  • Target version set to v1_6_0
  • % Done changed from 60 to 100

Tests for this feature are successful. This feature is scheduled to be deployed with CI v1_6_0

#4 Updated by Vito Di Benedetto about 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF