[SERVER-47186] Ensure parity of testing coverage between suites that run targeted transactions tests and suites that rely on the transactions override framework Created: 30/Mar/20  Updated: 06/Dec/22  Resolved: 01/Mar/21

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

Type: Improvement Priority: Major - P3
Reporter: Maria van Keulen Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

There are many test suites of the form *multi_stmt_txn*.yml, e.g., multi_stmt_txn_jscore_passthrough_with_migration.yml that rely on the transactions override framework to wrap non-transaction-related tests inside transactions. However, commands like create and createIndexes are not tested in the override framework, and rely on the core/txns/**.js tests instead.

These commands, as well as other potential future commands, are not realistic to test as part of the transactions override framework. We should ensure that the testing configurations available to the transactions override suites are also available to suites that run core/txns/**.js, wherever possible.



 Comments   
Comment by Connie Chen [ 01/Mar/21 ]

Execution team is confident there is enough test coverage in our current test suites, so closing this as "Won't do."

Generated at Thu Feb 08 05:13:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.