-
Notifications
You must be signed in to change notification settings - Fork 10
VIDSOL-280: Unit test fixes and configuration refinements #250
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
VIDSOL-280: Unit test fixes and configuration refinements #250
Conversation
d74028e to
a0d05c8
Compare
a0d05c8 to
18a230d
Compare
OscarFava
left a comment
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.
LGTM!
18a230d to
a0d05c8
Compare
|
fyi, some merge conflicts |
The merge-base changed after approval.
a0d05c8 to
6d8ac7f
Compare
OscarFava
left a comment
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.
LGTM!
Thanks! I already rebase with develop |
...c/Context/BackgroundPublisherProvider/useBackgroundPublisher/useBackgroundPublisher.spec.tsx
Show resolved
Hide resolved
frontend/src/components/MeetingRoom/ParticipantList/ParticipantList.spec.tsx
Show resolved
Hide resolved
6d8ac7f to
d3f10b6
Compare
behei-vonage
left a comment
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.
LGTM
d3f10b6 to
f973b34
Compare
Unit tests were not isolated, tests were unstable, and reliability was compromised.
f973b34 to
b7db2f7
Compare
|
rserebrennykov
left a comment
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.
LGTM
VZaphod
left a comment
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.
LGTM



What is this PR doing?
This pull request introduces the proper cleanups after each test to ensure that all mocks and global states are reset.
By enforcing isolation at the test environment level, we can immediately detect tests that rely on shared state or unclean mocks.
This change:
Once merged, this will make our Vitest suite more stable, maintainable, and aligned with industry best practices for React unit testing.
How should this be manually tested?
Check nothing is broken and tests are passing
What are the relevant tickets?
Resolves VIDSOL-280
Checklist
[x] Branch is based on
develop(notmain).[ ] Resolves a
Known Issue.[ ] If yes, did you remove the item from the
docs/KNOWN_ISSUES.md?[ ] Resolves an item reported in
Issues.If yes, which issue? Issue Number?