Fixed
Details
Assignee
Barak KorrenBarak Korren(Deactivated)Reporter
Barak KorrenBarak Korren(Deactivated)Blocked By
waiting for code reviewComponents
Priority
High
Details
Details
Assignee
Barak Korren
Barak Korren(Deactivated)Reporter
Barak Korren
Barak Korren(Deactivated)Blocked By
waiting for code review
Components
Priority
Created January 22, 2017 at 4:17 PM
Updated May 25, 2017 at 11:31 AM
Resolved January 24, 2017 at 12:16 PM
The 'suit-type' is parth of the OST suit name that determines which type of suit is it. For example: 'basic', 'upgrade', etc.
In various point it is important to know the suit-type to figure out where the testing suit will look for particular files. This is why the suit-type is often held in a separate variable.
To allow working with OST suits, it is desirable that the value of the 'suit-type' will be a consistent string everywhere. This is the case with the 'basic' suits, but this is not the case with suites like the (currently named) 'he_basic' suit.
For 'he_basic' (and other suites that have multi-worded names) the suit type is specified as 'he_basic' in YAML and in the names of the automation scripts, but as 'he-basic' in the name of the suit directory in the OST source repo.
In the CI system we typically regard underscore ('_') as a separator and hyphen ('-') as a joiner. So it is desirable to rename all the OST automation scripts and fix the YAML so that all OST suits will only have hyphens ('-') in their names.