[SERVER-23353] Make the test hook names hook more descriptive Created: 25/Mar/16 Updated: 18/May/16 Resolved: 18/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.3.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Robert Guo (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | TIG 13 (04/22/16), TIG 15 (06/03/16) |
| Participants: |
| Description |
|
The test hooks are currently called #hook_name# in Evergreen runs, which is confusing. They're going to get more confusing when JS hooks are added. we should modify hooks.py and add "after test hooks" or something to their names. |
| Comments |
| Comment by Robert Guo (Inactive) [ 18/May/16 ] |
|
This will be done as part of For an example of the new names, see: https://evergreen.mongodb.com/task/mongodb_mongo_master_osx_107_debug_jsCore_decimal_f2f6163b0b26f1b18951c3d4d0f88a833c344523_16_05_18_17_49_35 |
| Comment by Kyle Suarez [ 25/Mar/16 ] |
|
Not sure how this would look, but it would be nice if the hook indicated which other test it was being run after. |