[SERVER-74783] Improve serverStatus test coverages Created: 13/Mar/23  Updated: 29/Jan/24

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

Type: Engineering Test Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Pavithra Vetriselvan
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Replication
Sprint: Repl 2024-02-19
Participants:

 Description   

Atlas consumes the serverStatus output for a lot of things (e.g. InTel). And even a small behavior change in serverStatus output could break a Cloud dashboard. Ideally, those should be caught by Cloud testing during the rc period. But the large surface area makes it difficult or infeasible. So maybe it should be a joint effort from both Cloud and Server. This ticket is to think about how to improve the current serverStatus test coverages.

Most serverStatus tests I found in the Server repo are pretty basic and targeted. And it also seems impractical for the Server to test everything in all cases on a running MongoDB node. While I think it is difficult to test that everything is correct (i.e. every field reporting the exact value precisely), I think it might be easier if we just want to test everything has meaningful/valid value. Maybe we can explore extending fsm_workloads/server_status.js or adding a background hook to check the validity of serverStatus output while running the server test suites.


Generated at Thu Feb 08 06:28:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.