[SERVER-20730] Automatically detect parallel suite failures with prototype overrides Created: 01/Oct/15 Updated: 06/Dec/22 Resolved: 11/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.1.8 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||
| Participants: | |||||||||
| Description |
|
We can proactively detect potential failures in the parallel suite by using prototype overrides. For example, we can detect jsCore tests that use setParameter and immediately fail with an obvious error message that explains the issue. The idea comes from chatting with geert.bosch and max.hirschhorn. |
| Comments |
| Comment by Ryan Timmons [ 11/May/20 ] |
|
Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue. |