|
2016-05-08
| ||
| 21:56 | • Fixed ticket [cec6f1e7cc]: Dashboard not applying target when opening test window plus 2 other changes artifact: 8dbf764ebe user: matt | |
|
2015-09-08
| ||
| 10:01 | • Ticket [cec6f1e7cc]: 3 changes artifact: c5b4bc326f user: tyardeni | |
|
2015-09-03
| ||
| 17:13 | • Ticket [cec6f1e7cc]: 5 changes artifact: 8a78db918f user: tyardeni | |
| 17:09 | • New ticket [cec6f1e7cc]. artifact: dc22426a33 user: tyardeni | |
| Ticket Hash: | cec6f1e7cccf59ed29579724706a647f47b97aba | |||
| Title: | Dashboard not applying target when opening test window | |||
| Status: | Fixed | Type: | Code_Defect | |
| Severity: | Critical | Priority: | Immediate | |
| Subsystem: | Resolution: | Open | ||
| Last Modified: | 2016-05-08 21:56:15 | |||
| Version Found In: | 1.6023 | |||
| Description: | ||||
|
When clicking on a failure in megatestqa, the test window will not pop up.
When the issue was demonstrated, it looked like the target may not be getting passed along. The runconfig looks something like: [target] VAR1 foo VAR2 [system script #{rget VAR1}] | ||||
| User Comments: | ||||
tyardeni added on 2015-09-03 23:13:23:
Trying the runconfig snippet again:
[target]
VAR1 foo
VAR2 [system script #{rget VAR1}]
tyardeni added on 2015-09-08 16:01:50: After discussion, plan is to try not processing runconfig in launching of test control panel. Alternately, explicitly pass target. | ||||