Skip to content

Make standalone tests actually standalone #25

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

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

bartveneman
Copy link
Contributor

closes #24

Standalone tests were all using instances of Specificity instead of the actual standalone functions. Removed all the Specificity. prefixes after which the tests still run successfully.

@bramus
Copy link
Owner

bramus commented Feb 10, 2025

Good catch! Could you merge the latest HEAD onto this branch + update the newly added tests from #29? Then I can merge the whole lot :)

closes bramus#24

Standalone tests were all using instances of Specificity
instead of the actual standalone functions. Removed all
the `Specificity.` prefixes after which the tests still
run successfully.
@bramus bramus merged commit f7917fd into bramus:main Feb 10, 2025
3 checks passed
@bramus
Copy link
Owner

bramus commented Feb 13, 2025

FYI: In hindsight I realized this standalone test was not actually testing if the standalone exports work or not, as they imported the files directly. They also duplicated a bunch of tests that get run against the built file.

As a result I have updated the standalone test in e57cb88 so that it actually tests if the subpath exports do export the correct set of functions. Their functionality is not tested in that file, as that’s a responsibility of the other test that uses the built asset for its tests.

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 this pull request may close these issues.

Question: are standalone tests correct?
2 participants