-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#343 feat(domain) Aggregation Resilience #345
base: main
Are you sure you want to change the base?
Conversation
|
||
it('should give the valid posts only', async () => | ||
{ | ||
await remove(REQUESTERS.CREATOR1, VALUES.IDS.POST_RATED); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This remove call modifies the test fixtures to fit the test assertions below, basically saying that the fixtures do not support this test scenario. Instead of calling the remove function, we need to update the fixtures.
@@ -15,29 +15,45 @@ beforeEach(async () => | |||
|
|||
describe('domain/notification/getallAggregated', () => | |||
{ | |||
it('should give all posts for the requester', async () => | |||
it('should give all posts for the requester2', async () => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed before, this description should tell what scenario is tested. Getting the posts (notifications?) for requester 2 doesn't say anything. It should be clear what's wrong if this test case fails.
Quality Gate passedIssues Measures |
Fixes #
Changes proposed in this pull request:
@MaskingTechnology/comify