Forum Discussion

Bob_C's avatar
Bob_C
Contributor
2 years ago

Test Exectution Status for Cases that will not be run

We have a manual test cycle that we run through for a nightly (usually weekly) build that has a total of 25 test cases in it.   We require that our builds go through a complete test cycle, with all t...
  • MisterB's avatar
    MisterB
    2 years ago

    Interesting question.  Technically, if test case D, E, F, etc. are stopped because test case C has a bug, they are blocked (by your testing process), but I get what you mean and another status could help clarify things further.

     

    I don't know of an industry standard for that scenario but if I were creating a custom one, the ones that spring to mind are Halted or Stopped, but I have also seen and used Skipped, Deferred, Not Applicable, and Descoped.

     

    I think at the end of the day whatever you choose can be reported against and as long as it makes sense to you and everyone else, it'll work for your purposes 🙂

     

    Hope that helps.

Bob_C's avatar
Bob_C
Contributor
2 years ago

Thanks for the reply.  This is what I was looking for.  I had come up with some of those terms already, but thought it is better to ask someone else in the industry what makes the most sense.  

In this case, I think halted makes the most sense.  There may be some use for skipped in some situations.  I also don't want to get too crazy with these fields, as I have found that the closer you stick to a plain-vanilla system, the better it generally works.