[SERVER-56866] Leverage Feature Flag Information for Self-Testable-Installs Created: 11/May/21  Updated: 28/Aug/23  Resolved: 28/Aug/23

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

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-56744 All feature flags to be specified for... Closed
Assigned Teams:
Server Development Platform
Participants:

 Description   

For testing of functionality behind feature flags, we currently rely on a script to generate the list of all feature flags, turn all of them on, then run all tests with those feature flags. While this does provide sufficient test coverage, it is also quite inefficient, especially as we are also running the same set of tests without any feature flags.

It would be really nice to map a certain code change to affected feature flags.

Shorter term, we can generate a list of feature flags that have definitively not been modified so we don't have to run any tests against them.

Longer term, it would be nice to enforce mapping of tests to either feature flags and/or some other basic unit of functionality in the Server codebase so that a direct dependency chart of JS tests and C++ code changes can be drawn.


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