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.

Sign up for GitHub

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

Jump to bottom

Testing framework #57

Open
ldelelis opened this issue Sep 24, 2019 · 1 comment
Open

Testing framework #57

ldelelis opened this issue Sep 24, 2019 · 1 comment
Labels
enhancement New feature or request feat Feature suggestion/plan help wanted Extra attention is needed

Comments

@ldelelis
Copy link
Member

There's a bunch of critical functionality that's not apparent at first sight. We should define the expected behaviour for the kernel's "boot": module discovery, load, error handling, maybe logging?
@ldelelis ldelelis added enhancement New feature or request feat Feature suggestion/plan help wanted Extra attention is needed labels Sep 24, 2019
@ldelelis
Copy link
Member Author

Adding to the intent of the issue: how should we handle module testing? Should it be handled with the core's tests, or should whichever modules that need testing be turned into complex modules, with a tests directory?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request feat Feature suggestion/plan help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ldelelis