test: split multi-assertion specs into single-behavior tests
One behavior per test across FE machine/store specs and backend endpoint tests, so a failure names exactly what broke. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -242,9 +242,13 @@ describe('satisfaction helpers', () => {
|
||||
expect(categorySatisfied(s, 'diploma')).toBe(true);
|
||||
});
|
||||
|
||||
it('an active upload satisfies; a failed one does not', () => {
|
||||
let s = select(stateWith([cat()]), 'diploma', 'u1');
|
||||
it('an active upload satisfies a required category', () => {
|
||||
const s = select(stateWith([cat()]), 'diploma', 'u1');
|
||||
expect(categorySatisfied(s, 'diploma')).toBe(true);
|
||||
});
|
||||
|
||||
it('a failed upload does not satisfy a required category', () => {
|
||||
let s = select(stateWith([cat()]), 'diploma', 'u1');
|
||||
s = reduceUpload(s, { type: 'UploadFailed', localId: 'u1', reason: 'x' });
|
||||
expect(categorySatisfied(s, 'diploma')).toBe(false);
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user