[SERVER-55206] Consider adding a tag to disable an individual JavaScript test Created: 15/Mar/21  Updated: 06/Dec/22  Resolved: 15/Mar/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-33853 Define a new test tag to temporarily ... Closed
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

Thanks to the new BF process that is currently in pilot, there may be some increased need in the near future to be able to easily disable tests. Currently there are some idiomatic ways to exit early, e.g.

const disabled = true;
if (disabled) {
    return;
}

But these don't work uniformly for all suites. Some require more involved changes (e.g. FSM). In all such cases, the test still "runs", it just doesn't do anything.

It would be nice to have a simple and uniform way across suites to quickly disable a test until a fix can be made. A proposed solution would be something like a `test_disabled` tag.



 Comments   
Comment by Dan Larkin-York [ 15/Mar/21 ]

max.hirschhorn Ah, so it does! I had asked around in the execution team and collectively we didn't know about this. Will close and spread the good news. Thanks!

Comment by Max Hirschhorn [ 15/Mar/21 ]

dan.larkin-york, I believe this already exists as the __TEMPORARILY_DISABLED__ tag from SERVER-33853.

Generated at Thu Feb 08 05:35:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.