Megatest

View Ticket
Login
2017-04-24
16:25 Ticket [6606a69c0a] Megatest status rollup for test with items status still Open with 3 other changes artifact: 9144462522 user: bjbarcla
2017-04-19
09:14 Ticket [6606a69c0a]: 3 changes artifact: 3b404dc116 user: tyardeni
2017-04-13
18:00 Ticket [6606a69c0a]: 4 changes artifact: b603169d92 user: tyardeni
2016-11-23
10:48 Ticket [6606a69c0a]: 3 changes artifact: 35b65e1770 user: tyardeni
2016-11-22
10:27 Ticket [6606a69c0a]: 3 changes artifact: 9448cbe420 user: tyardeni
2016-03-08
15:53 Ticket [6606a69c0a]: 5 changes artifact: f9bbecf7d9 user: tyardeni
15:39 New ticket [6606a69c0a]. artifact: f6226b271b user: tyardeni

Ticket Hash: 6606a69c0a1459bfb5954ad02d918dd6a072b59f
Title: Megatest status rollup for test with items
Status: Open Type: Code_Defect
Severity: Severe Priority: Immediate
Subsystem: Resolution: Open
Last Modified: 2017-04-24 16:25:48
Version Found In: 1.6404
Description:
If a test has items, requesting update to the state/status of the top-level test to roll up.
User Comments:
tyardeni added on 2016-03-08 22:53:34:

For a test with items as below:

test/
  item1
  item2
  item3

Requesting that the top-level state/status be reflected as follows. Order of precedence/preference is top/down:

State/Status             Rolled up 
------------             ---------

RUNNING/%                RUNNING/RUNNING
REMOTEHOSTSTART/%        RUNNING/RUNNING
LAUNCHED/%               RUNNING/RUNNING

COMPLETED/CHECK          CHECK
COMPLETED/ABORT          ABORT
COMPLETED/FAIL           FAIL
NOT_STARTED/ZERO_ITEMS   FAIL
NOT_STARTED/TEN_STRIKES  FAIL

INCOMPLETE/%             INCOMPLETE/INCOMPLETE
KILLED or KILLREQ        KILLED

COMPLETED/WAIVED         WAIVED
COMPLETED/WARN           WARN
COMPLETED/PASS           PASS (all would have to be PASS)
COMPLETED/SKIP           SKIP


tyardeni added on 2016-11-22 17:27:48:
--UPDATE-- ABORT should probably supercede CHECK 


For a test with items as below:

test/
  item1
  item2
  item3

Requesting that the top-level state/status be reflected as follows. Order of precedence/preference is top/down:

State/Status             Rolled up 
------------             ---------

RUNNING/%                RUNNING/RUNNING
REMOTEHOSTSTART/%        RUNNING/RUNNING
LAUNCHED/%               RUNNING/RUNNING

COMPLETED/ABORT          ABORT
COMPLETED/CHECK          CHECK
COMPLETED/FAIL           FAIL
NOT_STARTED/ZERO_ITEMS   FAIL
NOT_STARTED/TEN_STRIKES  FAIL

INCOMPLETE/%             INCOMPLETE/INCOMPLETE
KILLED or KILLREQ        KILLED

COMPLETED/WAIVED         WAIVED
COMPLETED/WARN           WARN
COMPLETED/PASS           PASS (all would have to be PASS)
COMPLETED/SKIP           SKIP

tyardeni added on 2016-11-23 17:48:35:
--UPDATE-- New precedence, new state/status combos 


For a test with items as below:

test/
  item1
  item2
  item3

Requesting that the top-level state/status be reflected as follows. Order of precedence/preference is top/down. STATE=COMPLETED unless otherwise noted

State/Status             Rolled up 
------------             ---------

RUNNING/%                RUNNING/RUNNING
REMOTEHOSTSTART/%        RUNNING/RUNNING
LAUNCHED/%               RUNNING/RUNNING

ZERO_ITEMS/CHECK         ZERO_ITEMS/CHECK  => was NOT_STARTED/ZERO_ITEMS
INCOMPLETE/%             INCOMPLETE/CHECK 
KILLED or KILLREQ        KILLED/CHECK

COMPLETED/ABORT          ABORT
COMPLETED/CHECK          CHECK
TEN_STRIKES/CHECK        CHECK  => was NOT_STARTED/TEN_STRIKES
COMPLETED/FAIL           FAIL

COMPLETED/WAIVED         WAIVED
COMPLETED/WARN           WARN
COMPLETED/PASS           PASS (all would have to be PASS)
COMPLETED/SKIP           SKIP

NOT_STARTED/na           NOT_STARTED/na

tyardeni added on 2017-04-14 00:00:27:
--UPDATE-- THIS UPDATE TAKES PRECEDENCE AS OF 4/14/2017


For a test with items as below:

test/
  item1
  item2
  item3

Requesting that the top-level state/status be reflected as follows. Order of precedence/preference is top/down. Rolled up status is COMPLETED unless otherwise specified.

State/Status             Rolled up 
------------             ---------

RUNNING,%                RUNNING,RUNNING
REMOTEHOSTSTART,%        RUNNING,RUNNING
LAUNCHED,%               RUNNING,RUNNING

COMPLETED,ABORT          COMPLETED,ABORT
COMPLETED,CHECK          COMPLETED,CHECK
COMPLETED,FAIL           COMPLETED,FAIL
NOT_STARTED,%            INCOMPLETE,CHECK
NOT_STARTED,TEN_STRIKES  COMPLETED,CHECK


INCOMPLETE,%             INCOMPLETE,CHECK
KILLED or KILLREQ        KILLED,KILLED

COMPLETED,WAIVED         COMPLETED,WAIVED
COMPLETED,WARN           COMPLETED,WARN
COMPLETED,PASS           COMPLETED,PASS (all would have to be PASS or SKIP)
COMPLETED,SKIP           COMPLETED,SKIP (all would have to be SKIP)

tyardeni added on 2017-04-19 15:14:34:
--UPDATE-- THIS UPDATE TAKES PRECEDENCE AS OF 4/14/2017


For a test with items as below:

test/
  item1
  item2
  item3

Requesting that the top-level state/status be reflected as follows. Order of precedence/preference is top/down. Rolled up status is COMPLETED unless otherwise specified.

State/Status             Rolled up 
------------             ---------

RUNNING,%                RUNNING,RUNNING
REMOTEHOSTSTART,%        RUNNING,RUNNING
LAUNCHED,%               RUNNING,RUNNING

COMPLETED,ABORT          COMPLETED,ABORT
COMPLETED,FAIL           COMPLETED,FAIL
COMPLETED,CHECK          COMPLETED,CHECK

NOT_STARTED,%            INCOMPLETE,CHECK
NOT_STARTED,TEN_STRIKES  COMPLETED,CHECK


INCOMPLETE,%             INCOMPLETE,CHECK
KILLED or KILLREQ        KILLED,KILLED

COMPLETED,WAIVED         COMPLETED,WAIVED
COMPLETED,WARN           COMPLETED,WARN
COMPLETED,PASS           COMPLETED,PASS (all would have to be PASS or SKIP)
COMPLETED,SKIP           COMPLETED,SKIP (all would have to be SKIP)

bjbarcla added on 2017-04-24 22:25:48:
Decided:

Filters shall ignore status when state of test visited is not one of NOT STARTED or COMPLETED.

put another way:

When hiding, if statuses are selected, they do not filter tests that are not in NOT STARTED or COMPLETED state.