Forum Discussion

SlickRick's avatar
SlickRick
Frequent Contributor
11 months ago

Flagging Known Bugs

So i wrote some UI tests for some feature which have known bugs. Obviously those tests are currently failing because indeed the feature is broken. However in my azure pipeline i would those tests...
Desktop Testing
  • MW_Didata's avatar
    MW_Didata
    11 months ago

    I like to post a warning on top and disable the actions inside the Keywordtest, this way you can see what tests are disabld by the warning, and then just remove the warning an re-enable when it gets fixed: 

    If you use a ticket system you could post the ticket number in the warning.

Marsha_R's avatar
Marsha_R
Moderator

I would consider commenting out those tests until a fix is available. Are they adding any value at this point?

SlickRick's avatar
SlickRick
Frequent Contributor
11 months ago

I do feel like it would add value if i would be capable of flagging known issues the way i mentioned in my post.

This way some team members can code certain tests and if it is a bug, we can still see the pipeline being 'not considered' final until all features are fully working and all known bugs are fixed.

By disabling them, you need to rely on the developers to not forget to re-enable.

Of course not that of a big deal, but i do think there is value to be able to tag certain tests as failing with a known bug and be able to differentiate between a test which is failing but reported and waiting to be fixed vs a test failing due to a new problem