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

Layer tests #69

Open
Technologicat opened this issue Aug 29, 2020 · 2 comments
Open

Layer tests #69

Technologicat opened this issue Aug 29, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@Technologicat
Copy link
Owner

As a follow-up to #5, especially if we go the @typed route in #21, it's becoming important to layer the tests so that the lower levels (that other parts of unpythonic rely on) are tested first, to make it easier to find the bug when something fundamental breaks.

The runtests.py script executes the automated test modules in any given directory in lexicographical (a.k.a. "asciibetical"... nowadays maybe "unicodical"?) order, so this can be achieved by simply renaming the automated test files.

The tricky part is to figure out the proper ordering. As for the first layer, at least dynassign and typecheck, maybe also collections (box is used in other modules), should be part of that.

@Technologicat Technologicat added the enhancement New feature or request label Aug 29, 2020
@Technologicat Technologicat added this to the 0.14.3 milestone Aug 29, 2020
@Technologicat Technologicat self-assigned this Aug 29, 2020
@Technologicat
Copy link
Owner Author

Hmm, maybe we can use pyan3's modvis.py to find modules which have no outgoing edges, i.e. those that don't depend on anything else.

If there's at least a partial order in the dependency graph, that could point the way forward in a semi-automated way...

@Technologicat Technologicat changed the title Ordering of tests Layer tests Sep 4, 2020
@Technologicat
Copy link
Owner Author

Layer 0: since our no-framework (cf. "NoSQL") unpythonic.test.fixtures is programmable, we can test its lower-level functionality first (using plain asserts), before we run the rest of the tests.

@Technologicat Technologicat modified the milestones: 0.14.3, 0.14.5 Sep 11, 2020
@Technologicat Technologicat modified the milestones: 0.14.5, 0.15.x Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant