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

CLI tests should not be stateful #5482

Closed
kayagokalp opened this issue Jan 17, 2024 · 0 comments · Fixed by #5589
Closed

CLI tests should not be stateful #5482

kayagokalp opened this issue Jan 17, 2024 · 0 comments · Fixed by #5589
Assignees
Labels
forc testing General testing

Comments

@kayagokalp
Copy link
Member

kayagokalp commented Jan 17, 2024

We have cli tests introduced in #5388, one problem with the implementation is that some actions are stateful, this is not a problem in CI as instances are killed after each run, but as sway repo developers our local systems should not be affected with tests running. Currently, a wallet is created in the default path this is not good for developer experience and also creates problems if the developer has a wallet in the default path. As forc-deploy/wallet stuff we might have other stateful things in the cli tests. We should consider changing the behaviour so that anything that effects the system etc are cleaned after tests ran.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
forc testing General testing
Projects
None yet
2 participants