You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
At https://github.com/keep-starknet-strange/madara we are building starknet sequencers.
Other projects are doing so and others are building full nodes.
All are expected to integrate with starknet.js seamlessly.
The issue is that we don't have the expertise to keep this suite of tests up to date with your lib upgrade, so it ends up breaking for bad reasons.
Describe the solution you'd like
We would like you, to write and maintain such a test suite, keep it always up to date with your every release, and expose it as a simple and efficient gh action.
The text was updated successfully, but these errors were encountered:
Hello,
For short term, you can do the same thing than Lava project : use manually the Starknet.js test suite, not to test Starknet.js, but to test their nodes.
For longer term, I will soon have a look at this subject.
To be able to contact you directly, what's your Discord Id (mine is @Phil26)?
Is your feature request related to a problem? Please describe.
At https://github.com/keep-starknet-strange/madara we are building starknet sequencers.
Other projects are doing so and others are building full nodes.
All are expected to integrate with starknet.js seamlessly.
Right now we are trying to maintain this compatibility in our CI with a custom suite of tests we wrote that cover most of the lib features. You can find this repo here: https://github.com/keep-starknet-strange/sequencer-js-compatibility-tests. It is used as a gh action in madara.
The issue is that we don't have the expertise to keep this suite of tests up to date with your lib upgrade, so it ends up breaking for bad reasons.
Describe the solution you'd like
We would like you, to write and maintain such a test suite, keep it always up to date with your every release, and expose it as a simple and efficient gh action.
The text was updated successfully, but these errors were encountered: