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

Integrate launchTestNode with current test suites #1820

Open
arboleya opened this issue Feb 29, 2024 · 2 comments · May be fixed by #2579
Open

Integrate launchTestNode with current test suites #1820

arboleya opened this issue Feb 29, 2024 · 2 comments · May be fixed by #2579
Assignees
Labels
bug Issue is a bug chore Issue is a chore p0 High priority
Milestone

Comments

@arboleya
Copy link
Member

The idea is to update tests to use an isolated node via launchTestNode.

Then, we can try running tests in parallel / concurrently again.

Past experiments have been successful in this regard.


Must be done after:

And will probably fix:

@arboleya
Copy link
Member Author

@nedsalk It would be fantastic to have a draft PR for this, after:

Like a small POC proving the workings of the former and demoing it in the real world.

cc @danielbate

@arboleya arboleya added p1 Medium priority and removed mainnet labels Jun 9, 2024
@arboleya arboleya added bug Issue is a bug and removed p1 Medium priority labels Jun 12, 2024
@arboleya arboleya added this to the 0.x mainnet milestone Jun 12, 2024
@maschad maschad added the p0 High priority label Jun 17, 2024
@danielbate
Copy link
Contributor

As part of this and with the merging of #2378, can we add the @group browser tag to tests also? The imports will need to be using the typegen paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue is a bug chore Issue is a chore p0 High priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants