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

test: add tests for wallets/react #824

Open
wants to merge 8 commits into
base: next
Choose a base branch
from

Conversation

yeager-eren
Copy link
Collaborator

@yeager-eren yeager-eren commented Aug 7, 2024

Summary

Add integration tests for walelt-react.

This PR includes some integration tests for legacy provider and also some todo tests for doing for future.

Fixes RF-1731

How did you test this change?

Run yarn test

Related PRs

Checklist:

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • Implemented a user interface (UI) change, referencing our Figma design to ensure pixel-perfect precision.

Notes

First I need to change connect interface for legacy.

@yeager-eren yeager-eren marked this pull request as draft August 7, 2024 11:15
@yeager-eren yeager-eren changed the title WIP! chore: moving test. but we need to change legacy interface first WIP! chore: add tests for wallets/react Aug 7, 2024
@yeager-eren yeager-eren mentioned this pull request Aug 7, 2024
2 tasks
@yeager-eren yeager-eren force-pushed the chore/rf-1731-wallets-react-tests branch 2 times, most recently from ca2a758 to 98dec66 Compare October 5, 2024 08:40
@yeager-eren yeager-eren changed the base branch from next to feat/support-for-both-legacy-and-hub October 5, 2024 08:42
legacyProvider,
} from '../src/test-utils/fixtures.js';

describe('check legacy is working correctly', () => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
describe('check legacy is working correctly', () => {
describe('legacy is working correctly', () => {

I think "check" is redundant

});
});

describe('check legacy switching network', () => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
describe('check legacy switching network', () => {
describe('legacy switch network works properly', () => {

I think it would be helpful if you follow a specific convention

);
});

test('will be ignored and use first namespace when passing multiple namespaces', async () => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have added a comment related to this test on adapter PR

@yeager-eren yeager-eren force-pushed the feat/support-for-both-legacy-and-hub branch from ab16aea to 9355468 Compare October 30, 2024 09:11
@yeager-eren yeager-eren force-pushed the feat/support-for-both-legacy-and-hub branch from 9355468 to 1f9f637 Compare October 30, 2024 09:15
@yeager-eren yeager-eren force-pushed the feat/support-for-both-legacy-and-hub branch 2 times, most recently from f0db76c to 455bafc Compare November 20, 2024 12:19
@yeager-eren yeager-eren force-pushed the feat/support-for-both-legacy-and-hub branch 2 times, most recently from 27f3bbe to 63f00c5 Compare December 1, 2024 07:36
Base automatically changed from feat/support-for-both-legacy-and-hub to next December 1, 2024 07:53
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