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.

Sign up for GitHub

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

Jump to bottom

Improve Unit Test Coverage #118

Closed
radicleart opened this issue May 5, 2023 · 2 comments
Closed

Improve Unit Test Coverage #118

radicleart opened this issue May 5, 2023 · 2 comments

Comments

@radicleart
Copy link
Collaborator

radicleart commented May 5, 2023 •
edited

The sbtc bridge unit tests have evolved through several pivots in the core functionality.

This issue requires;

  1. Tests to be stabilised - all tests must be properly mocked to avoid intermittent test failures - no external http requests to be made by running the tests
  2. Svelte component test coverage - coverage of the svelte components needs to be improved to 50%
  3. Typescript classes / file - coverage needs to improved to 80%

The tests need to be better organised and structured.

Note: we get test failures upgrading noble/secp256 to v2 see this Issue. Ideally this issue should include a fix for this.
@radicleart radicleart changed the title Improve Test Coverage Improve Unit Test Coverage May 5, 2023
@igorsyl
Copy link
Contributor

igorsyl commented May 5, 2023

cc @sergey-shandar as he is owning technical leadership of Testing Infra across sBTC including UI/UX.

@radicleart
Copy link
Collaborator Author

closing as fixed by other work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@igorsyl @radicleart