[SERVER-65339] add namespace to the filename tests Created: 07/Apr/22 Updated: 29/Oct/23 Resolved: 04/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Moody | Assignee: | Richard Samuels (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v6.0, v5.0, v4.4
|
||||
| Sprint: | Dev Platform 2022-05-02, Dev Platform 2022-05-16 | ||||
| Participants: | |||||
| Description |
|
Many of the tests can be called directly from the command line by just using the test name, but this also puts a requirement that the source files have globally unique names. If we add a namespace to the test, then we can avoid this limitation. For example theĀ cancelable_operation_context_test lives in the db_unittest_test binary, so if we added namespacing, the test would now be invoked via +db_unittest_cancelable_operation_context_test. The main drawback is the length of the names will become much larger. This may not matter much considering autocomplete features available. |
| Comments |
| Comment by Githook User [ 04/May/22 ] |
|
Author: {'name': 'Richard Samuels', 'email': 'richard.l.samuels@gmail.com', 'username': 'richardsamuels'}Message: |