[SERVER-32737] Add javascript tests for common transactions use cases Created: 17/Jan/18 Updated: 27/Oct/23 Resolved: 27/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Sprint: | Repl 2018-03-12, Repl 2018-04-23 | ||||
| Participants: | |||||
| Description |
|
We should add some integration tests based around common use cases for transactions early. We should start with the ones that can be implemented with doTxn now, and update them to use the multi-statement machinery when it's available. We should also try to figure out what other use cases we would want to test that can't be tested with just doTxn, but could be once we have read-write transaction support. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 27/Mar/18 ] |
|
We will be filing specific SERVER tickets for individual tests described in the transactions test plan once it is finalized |