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

Include dev-dependencies in test compilation #1460

Closed
piotmag769 opened this issue Jan 2, 2024 · 1 comment · Fixed by software-mansion/scarb#1033
Closed

Include dev-dependencies in test compilation #1460

piotmag769 opened this issue Jan 2, 2024 · 1 comment · Fixed by software-mansion/scarb#1033
Assignees
Labels
bug Something isn't working snforge test-collector

Comments

@piotmag769
Copy link
Member

The simplest solution may be to prioritize test target over starknet-contract target here, but it has to be investigated if it works.
Appropriate tests should be added.

@piotmag769
Copy link
Member Author

PR: software-mansion/scarb#1033

github-merge-queue bot pushed a commit to software-mansion/scarb that referenced this issue Jan 8, 2024
Closes foundry-rs/starknet-foundry#1460

The solution is to fetch dependencies from unit test compilation unit.

After talking with @mkaput we decided that to ensure this heuristic
solution doesn't break we check if all other test compilation units have
the same dependencies (excluding dependencies being sources for
integration tests i. e., starting with `{package_path}/tests/`).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working snforge test-collector
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant