Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Replication
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

A test in noPassthrough provides very limited test coverage, whereas tests in jstests/core are run with all the configurations / fault tolerance modes available in our passthroughs. They will also be picked up by any new suite that is added in the future, so in that way they help with future coverage as well.

We may have to break this into multiple tickets to be assigned to each team instead.

related to

SERVER-87095 Service Arch: audit and move noPassthrough / noPassthroughWithMongod tests into jstests/core

Open

SERVER-87096 Replication: audit and move noPassthrough / noPassthroughWithMongod tests into jstests/core

Open

SERVER-87093 Cluster Scalability: audit and move noPassthrough / noPassthroughWithMongod tests into jstests/core

Backlog

SERVER-87094 Security: audit and move noPassthrough / noPassthroughWithMongod tests into jstests/core

Backlog

SERVER-81927 Move noPassthrough timeseries tests into core

Closed

SERVER-87092 StorEx: audit and move noPassthrough / noPassthroughWithMongod tests into jstests/core

Closed

SERVER-87097 Query: audit and move noPassthrough / noPassthroughWithMongod tests into jstests/core or jstests/aggregation

Needs Scheduling

(2 related to)

Assignee:: Unassigned
Reporter:: Vishnu Kaushik
Participants:: Vishnu Kaushik
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Feb 21 2024 04:30:07 PM UTC
Updated:: Jul 29 2024 05:00:21 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates