2017-08-03
| ||
13:56 | • Ticket [6abf4531ea] Add capability to override default testpatt var status still Open with 3 other changes artifact: 42d1f61f20 user: tyardeni | |
13:56 | • Ticket [6abf4531ea]: 3 changes artifact: 253e3953f7 user: tyardeni | |
2016-09-14
| ||
11:56 | • Ticket [6abf4531ea]: 5 changes artifact: 19d83e3c2d user: tyardeni | |
11:55 | • New ticket [6abf4531ea]. artifact: 73c7a6caf1 user: tyardeni | |
Ticket Hash: | 6abf4531ea33f169bb647058b7c6943a76f1abaa | |||
Title: | Add capability to override default testpatt var | |||
Status: | Open | Type: | Feature_Request | |
Severity: | Important | Priority: | Immediate | |
Subsystem: | Resolution: | Open | ||
Last Modified: | 2017-08-03 13:56:50 | |||
Version Found In: | ||||
Description: | ||||
Current behavior in megatest is to look in runconfig for a TESTPATT setting if a testpatt is not specified on the command line.
This request is to enhance the behavior to add a -testpattvar parameter that takes a runconfig setting name to use for the default testpatt. The testpattvar should be an optional argument that defaults to TESTPATT. Sample usage: megatest -run -runname foo -target foo/bar -testpattvar FOOPATT. | ||||
User Comments: | ||||
tyardeni added on 2016-09-14 17:56:25:
Suggested behavior if the variable specified in -testpattvar does not exist in runconfig is to exit cleanly with an error and display an error message stating that the specified testpattvar does not exist in runconfig. This behavior could also apply if the default TESTPATT is not specified. tyardeni added on 2017-08-03 19:56:27: Extending this request to support multiple test patterns, to be checked in the order supplied. If none of the given variables exist in runconfig, exit with an error: eg: -testpattvar MODE1PATT,MODE2PATT |