[SERVER-49303] Properly assert that expected log messages are present in invalid_index_spec.js and initial_sync_invalid_index_spec.js Created: 02/Jul/20 Updated: 27/Oct/23 Resolved: 28/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Wlodarek |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Execution Team 2021-06-14 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
In invalid_index_spec.js and initial_sync_invalid_index_spec.js, we verify whether a log message is present using
However, the search() function returns the index of the first match, or -1 if there was no match. Thus, the current usage does not properly assert that the log message is present. These should be changed to either
|
| Comments |
| Comment by Gregory Wlodarek [ 28/May/21 ] |
|
Closing this ticket as 'gone away' as both tests have been deleted.
|