Skip to content
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

Refactor: Increase testing coverage for extension package #520

Merged
merged 23 commits into from
Apr 9, 2024

Conversation

amovar18
Copy link
Collaborator

@amovar18 amovar18 commented Feb 22, 2024

Description

This PR aims to increase testing coverage for the extension package.

Relevant Technical Choices

Testing Instructions

Additional Information:

Screenshot/Screencast


Checklist

  • I have thoroughly tested this code to the best of my abilities.
  • I have reviewed the code myself before requesting a review.
  • This code is covered by unit tests to verify that it works as intended.
  • The QA of this PR is done by a member of the QA team (to be checked by QA).

@amovar18 amovar18 self-assigned this Feb 22, 2024
@amovar18 amovar18 force-pushed the ref/add-test-coverage-extension branch 2 times, most recently from b9bcc4f to 8dc024b Compare February 22, 2024 12:25
@mohdsayed mohdsayed added this to the v0.7.0 milestone Mar 12, 2024
Base automatically changed from ref/service-worker-provider to develop March 28, 2024 13:07
@amovar18 amovar18 marked this pull request as ready for review April 5, 2024 08:33
@amovar18 amovar18 requested a review from mohdsayed April 5, 2024 08:34
@amovar18 amovar18 requested review from ayushnirwal and removed request for mohdsayed April 5, 2024 08:34
@mohdsayed mohdsayed merged commit e50dad8 into develop Apr 9, 2024
1 check passed
@mohdsayed mohdsayed deleted the ref/add-test-coverage-extension branch April 9, 2024 04:00
@mohdsayed mohdsayed mentioned this pull request Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants