-
Notifications
You must be signed in to change notification settings - Fork 177
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
Fix test name resolving logic #62
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Aug 7, 2023
<!-- Reference any GitHub issues resolved by this PR --> Closes #62 ## Introduced changes <!-- A brief description of the changes --> - Replaced `src` with package name in test collecting. - Removed duplication of file names of tests outside the package tree. - Removed `setup_project` function and replaced usage of it with `setup_single_file_project`, as the remaining if branch in `setup_project` wasn't used anyways. Did similar thing with library collection. ## Breaking changes <!-- List of all breaking changes, if applicable --> ## Checklist <!-- Make sure all of these are complete --> - [x] Linked relevant issue - [x] Updated relevant documentation - [x] Added relevant tests - [x] Performed self-review of the code
Utilitycoder
pushed a commit
to Utilitycoder/starknet-foundry
that referenced
this issue
Oct 6, 2023
* Fixed some typos * fix(arrays): remove mut attribute --------- Co-authored-by: msaug <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
software-mansion/protostar#2093
Compiler's
collect_tests
adds whole paths in the filesystem to test names that are defined inline with the implementation.e.g.
/abs/path/to/file/src::test_fib
instead of just
src::test_fib
In #1999 basic handling for this was added by just stripping the path from the name.
We should introduce the required changes to test collecting so paths are not included in the first place and remove the stripping logic.
There's a high chance this is related to #2092, so we should first resolve #2092 before starting this issue.
The text was updated successfully, but these errors were encountered: