Quarantine feature for AET

szymon-owczarzak commented 6 years ago

Version used

AET 2.1.5

Context of the issue/feature

We use AET a lot in our project. We often come to a situation when there is a unwanted change visible in our suite and we know that it will be fixed in near future. In this case we neither want to accept this change nor be bothered by it every day until it is fixed. For this kind issues that are valid by will be fixed in future we need a quarantine feature.

Feature description

After discussion that took place on 11th of May 2018 by @Skejven @wiiitek @szymon-owczarzak we came up with this ideas:

[ ] Quarantine feature should be available next to Note feature on every level (Suite, Test, Url, Case)
[ ] We could use either clock or calendar icon for Quarantine action button
[ ] After clicking Quarantine action - modal window with Date Picker should be shown
[ ] There should be also an option to delete Quarantine until - date
[ ] Quarantine action should behave similar to Note action when it comes to look and feel (colors) and saving changes

Indication of elements that are in quarantine:

Suite level:

if Suite is in quarantine ??? TBD
Test level:
if Test is in quarantine Test tile is marked by grey background and by Quarantine icon
URL level:
if Url is in quarantine parent Test tile is marked by Quarantine icon
if Url is in quarantine Url tile is marked by grey background and by Quarantine icon
Case level:
if Case is in quarantine parent Test tile is marked by Quarantine icon
if Case is in quarantine parent Url tile is marked by Quarantine icon
if Case is in quarantine Case tab is marked by grey background and tabs label bar has additional note Ignored

Additional notes

All test should be run even if they are in Quarantine
Only additional flag is added to test results when element is in Quarantine
Most of Quarantine feature should be driven by client side and not by backend
Probably backed changes will be responsible only for adding flag to results and store quarantine records
We need to assure that client and backed are working on the same Timezone

toniedzwiedz commented 6 years ago

Sounds like a very useful feature. I'd love to be able to use it on my project.

radeklawgmin commented 6 years ago

What about the case when:

the user spots a difference (e.g. some layout change on the mobile viewport) that she/he does want to be bothered with, so she/he makes use of the Quarantine feature
then it turns out that there is the other layout change on the same page?

Are we able to make the first change (the one that had been spotted before the user made use of the Quatantine feature) a kind of 'sub-pattern' or 'Quatantine pattern' with some threshold so that the user is alerted once the other change departing from the standard defined by her/him in the threshold for this case appears on the page?

mchrominski commented 6 years ago

I believe this should be achievable by storing the quarantined pattern but I suggest dropping this requirement for two reasons:

simplicity of the solution and feature
an already existing ability to achieve what you mentioned by reasonable pattern normalisation - testing single feature on one test

wttech / aet