-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
RSS Sydney
-
meow meow meow - 2025-04-15
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We want to tag our CPP unittests so that they can be run with a bazel one liner such as:
bazel test --test_tag_filters=server-rss-sydney-smoke //src/mongo...
rss-tooling/scripts/identify_tests.sh contains a script to identify the cpp files owned by our team. Using this list, work out which cpp files are test files, and which major project they belong to (out of validation, backup/restore, dbcheck). We want to create a subsuite for each of these areas, and an overall suite for the team.
These tests can be tagged in the bazel files so that the above bazel command can run them.
We want each suite to run as fast as possible, so when done, determine the runtime of each (all should be 1-2 mins max). If needed we can either optimize the tests or skip them if they are too slow
In the end state the above command should run quickly and give us signal about our code changes