Skip to content
This repository was archived by the owner on Nov 2, 2021. It is now read-only.

Improve test coverage #28

Open
HerrBertling opened this issue Jan 28, 2019 · 2 comments
Open

Improve test coverage #28

HerrBertling opened this issue Jan 28, 2019 · 2 comments

Comments

@HerrBertling
Copy link
Contributor

Right now, the test coverage across the different packages is rather low:

image

I'd like to improve this quite a bit to make future work on the packages a bit more secure. Can't pin down a definite percentage I want to achieve since a) I don't know whether I'm able to test everything and b) I currently have no idea which parts need testing and which can do without 😆

Something at ~50% seems like a good first shot, though.

@svewag @escapedcat @Xiphe @fdietz If anyone of you has input here, feel free to comment :)

@escapedcat
Copy link
Contributor

For me it's hard to pin a number to it. Depending on the functions and the context the percentage could vary quite a bit I think. In some projects 30% could be enough. Depends :P

@Xiphe
Copy link
Contributor

Xiphe commented Feb 20, 2019

I would also rather focus on adding some cypress/e2e tests that ensure that the developer-facing-API works as expected.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants