Support

Expand all | Collapse all

Test Case Status behaviour

  • 1.  Test Case Status behaviour

    Posted 11-24-2017 04:17
    Hello,

    I noticed two behaviours with the Test Case Status:
    - When a Test Run is Failed in, at least one, active Test Plan, the Test Case Status is Failed.
    - The Test Case Status contains the status of the last Test Run done.

    The user guide seems to say that the first behaviour is the right one.

    Someone could help me understand?

    Version of Jama: 8.10.2
    Production Environment
    Chrome

    Thank you.

    ------------------------------
    Xavier ROUAULT
    ------------------------------


  • 2.  RE: Test Case Status behaviour

    Posted 12-04-2017 15:18
    Hi Xavier,

    Both are correct. The Test Case Status is a field derived from the lowest status of the last executed Test Run in an active Test Plan.  Here is an article that gives more details.


    ------------------------------
    Rosemary Joe
    Jama Software
    ------------------------------



  • 3.  RE: Test Case Status behaviour

    Posted 12-05-2017 05:25
    Hi rosemary,

    First, thank you for your answer.

    What I'm trying to understand is why I have the two behaviors at the same time.

    In fact, we use multiple test plans/test cycles containing the same Test Cases.
    Without archiving any  test plan, sometimes the status "Failed" prevails on all the other results, no matter if the last result is a Passed, and sometimes only the last result is taken into account.

    We have some Test Cases that are Failed and remains Failed whatever the number of new runs that are Passed and other Test Cases that are Passed even if one of their runs is Failed.

    Best regards,

    ------------------------------
    Xavier ROUAULT
    ------------------------------



  • 4.  RE: Test Case Status behaviour

    Posted 12-06-2017 17:56
    Hi Xavier,

    Can I get some screenshots of the two behaviors at the same time?  Please include in the screenshots - test case status, test plan, and test run status.

    ------------------------------
    Rosemary Joe
    Jama Software
    ------------------------------



  • 5.  RE: Test Case Status behaviour

    Posted 12-07-2017 07:59
    Sometimes you might have a false testcase status for some testcases. You can fix that by archiving all testplans and un-archive the testplans you want to be considered.

    regards
    Harald

    ------------------------------
    Harald Hotz-Behofsits
    Frequentis AG
    ------------------------------



  • 6.  RE: Test Case Status behaviour

    Posted 12-14-2017 09:40
    Now, I understand the two behaviours.

    Thanks to both of you.

    ------------------------------
    Xavier ROUAULT
    ------------------------------



  • 7.  RE: Test Case Status behaviour

    Posted 03-08-2018 02:37
    What Harald describes, seems to happen much more frequently when there are many Test Runs / Cycles. This is really annoying. 

    ------------------------------
    Kasper Hansen
    GN Netcom

    ------------------------------



  • 8.  RE: Test Case Status behaviour

    Posted 09-26-2018 07:57
    The bug described above by Harald (on 12-07-2017), makes it really hard for us to do proper test management in Jama!

    We'd really like Jama to prioritize this bug. Please comment. 


    ------------------------------
    Kasper Hansen
    GN Netcom
    ------------------------------



  • 9.  RE: Test Case Status behaviour

    Posted 09-26-2018 13:39
    Kasper:

    This bug has been prioritized as a defect to be fixed. The defect where: Test Case Status is incorrectly representing Test Run results, has a Ready to be Developed status. You can look in the Release Notes in the Community for this bug key: SOS-DEF-2699 to see if it has gotten fixed in the next releases.


    Best,

    ------------------------------
    Chloe Elliott
    Jama Software
    ------------------------------



  • 10.  RE: Test Case Status behaviour

    Posted 10-15-2018 18:11
    ​I encountered the same problem (Test Cases inconsistently reporting the status of the most recently run Test Runs).
    I finally figured out that the "most recent" test is defined as the test with the most recent MODIFICATION date. So if a failed Test Run is edited after a passing Test Run is conducted, the results of that failed test will supersede those of the 2nd run.  So, when that happens, the workaround is to simply modify (in any way) the Test Run that is intended to be the "Most Recent" test.

    ------------------------------
    Kevin
    Washington River Protection Solutions (WRPS)
    ------------------------------