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

Nitro Testnode - Smoke test where each nitro component runs separately #222

Closed
Sneh1999 opened this issue Sep 4, 2024 · 1 comment
Closed
Assignees

Comments

@Sneh1999
Copy link

Sneh1999 commented Sep 4, 2024

Is your feature request related to a problem? Please describe.

Add an E2E test in the nitro-testnode repo that runs all components of the Nitro stack separately. This will help catch errors that might otherwise go unnoticed, such as bugs that aren't detected by the E2E tests in the nitro-espresso-integration repo, which currently uses the same storage for all Nitro components.

@Sneh1999 Sneh1999 self-assigned this Sep 5, 2024
@Sneh1999 Sneh1999 changed the title Nitro Testnode - Smoke test where each nitro component runs seperately Nitro Testnode - Smoke test where each nitro component runs separately Sep 6, 2024
@Sneh1999
Copy link
Author

Sneh1999 commented Sep 6, 2024

No work needs to be done here because when espresso flag is specified, the simple mode is turned off which results in all components in the nitro stack to be run separately ( code here)

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

No branches or pull requests

1 participant