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

Add integration tests for specific cheatcodes #2124

Closed
cptartur opened this issue Jun 26, 2023 · 2 comments
Closed

Add integration tests for specific cheatcodes #2124

cptartur opened this issue Jun 26, 2023 · 2 comments
Assignees

Comments

@cptartur
Copy link
Member

cptartur commented Jun 26, 2023

Instead of running e2e tests for each of the cheatcodes, we should design some general e2e tests and only run specific cheatcodes in integration tests. This will avoid having to run a whole application binary for each cheatcode.

@cptartur cptartur added this to the Rust test runner milestone Jun 26, 2023
@Arcticae
Copy link
Member

Consider using scarb's approach

@Arcticae
Copy link
Member

If mocking significant part of protostar is needed we should not proceed, a POC for this kind of tests would be nice

@piotmag769 piotmag769 self-assigned this Jun 27, 2023
@piotmag769 piotmag769 linked a pull request Jun 30, 2023 that will close this issue
3 tasks
@cptartur cptartur assigned cptartur and unassigned piotmag769 Jul 3, 2023
@piotmag769 piotmag769 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2023
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 a pull request may close this issue.

3 participants