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

Add Unit Test coverage #18

Closed
NeonDaniel opened this issue Dec 8, 2021 · 3 comments
Closed

Add Unit Test coverage #18

NeonDaniel opened this issue Dec 8, 2021 · 3 comments
Assignees
@NeonKirill
Labels
enhancement New feature or request

Comments

@NeonDaniel
Copy link
Member

No description provided.

@NeonDaniel NeonDaniel added the enhancement New feature or request label Dec 8, 2021
@NeonKirill NeonKirill mentioned this issue Dec 28, 2021
Merged
@NeonKirill
Copy link
Collaborator

NeonKirill commented Sep 13, 2023 •
edited
Loading

@NeonDaniel testing is a very broad topic, and as currently its only me part-time and rarely @NeonBohdan who maintain this repo, it may be considered less prioritized task. However, if there are any particular scenarios you feel like must be validated please mention those

@NeonDaniel
Copy link
Member Author

As mentioned in #64, I think util modules may make sense to be moved to and imported from neon-utils (with unit tests). I am unaware of a convenient way to test the webserver components and agree we are limited on resources to investigate it further.

@NeonKirill
Copy link
Collaborator

Closing this as for now there is insufficient development resources to imply end-to-end testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NeonKirill NeonKirill

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NeonDaniel @NeonKirill