Skip to content

Commit

Permalink
Fix NoRegression test as it contained paths
Browse files Browse the repository at this point in the history
  • Loading branch information
dubzzz committed Nov 27, 2019
1 parent 78d2f98 commit 5121fa6
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 16 deletions.
2 changes: 1 addition & 1 deletion test/e2e/NoRegression.spec.ts
Expand Up @@ -290,7 +290,7 @@ describe(`NoRegression`, () => {
});
}
await s.waitAll();
expect(received.join('')).not.toContain('aBc');
return !received.join('').includes('aBc');
}),
settings
)
Expand Down
15 changes: 1 addition & 14 deletions test/e2e/__snapshots__/NoRegression.spec.ts.snap
Expand Up @@ -2114,20 +2114,7 @@ Counterexample: [Scheduler\`
-> [task#6] promise resolved with value \\"C\\"
-> [task#5] promise resolved with value \\"A\\"\`]
Shrunk 0 time(s)
Got error: Error: expect(received).not.toContain(expected) // indexOf
Expected substring: not \\"aBc\\"
Received string: \\"baBcCA\\"
Stack trace: Error: expect(received).not.toContain(expected) // indexOf
Expected substring: not \\"aBc\\"
Received string: \\"baBcCA\\"
at C:\\\\dev\\\\fast-check\\\\test\\\\e2e\\\\NoRegression.spec.ts:293:41
at step (C:\\\\dev\\\\fast-check\\\\node_modules\\\\tslib\\\\tslib.js:136:27)
at Object.next (C:\\\\dev\\\\fast-check\\\\node_modules\\\\tslib\\\\tslib.js:117:57)
at fulfilled (C:\\\\dev\\\\fast-check\\\\node_modules\\\\tslib\\\\tslib.js:107:62)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Got error: Property failed by returning false
Execution summary:
√ [Scheduler\`
Expand Down
2 changes: 1 addition & 1 deletion test/unit/check/arbitrary/AsyncSchedulerArbitrary.spec.ts
Expand Up @@ -21,7 +21,7 @@ describe('AsyncSchedulerArbitrary', () => {
const s = scheduler().generate(mrng).value;

// Assert
expect(s.waitOne()).rejects.toMatchInlineSnapshot(`[Error: No task scheduled]`);
await expect(s.waitOne()).rejects.toMatchInlineSnapshot(`[Error: No task scheduled]`);
});
});

Expand Down

0 comments on commit 5121fa6

Please sign in to comment.