[SERVER-23743] resmoke.py hooks should create a new TestCase for each run of the hook Created: 15/Apr/16  Updated: 29/Jan/18  Resolved: 30/May/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.3.4
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Done Votes: 0
Labels: tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

Each resmoke.py hook currently use one TestCase for the entire suite and will only return when the entire suite has finished. If there are multiple jobs and one of them hangs, resmoke will report that the hooks ran for the duration of the hang, which can easily mislead the reader into believing the hooks are the cause of the hang.

We should have each run of the hook create a new TestCase (in CustomBehavior.after_test), and a separate TestCase for the summarized report that prints "hook succeeded for all tests in the suite" at the end.



 Comments   
Comment by Robert Guo (Inactive) [ 30/May/17 ]

This issue was fixed after work over the previous years to port some hooks over to JS and changes in SERVER-26522 for CleanEveryN. Each hook now calls start_dynamic_test, which will generate a new item to report.json.

The issue reported in this ticket has gone away.

Generated at Thu Feb 08 04:04:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.