Skip to content
This repository has been archived by the owner on Jun 3, 2022. It is now read-only.

Improve code coverage #19

Closed
utybo opened this issue Mar 28, 2022 · 1 comment
Closed

Improve code coverage #19

utybo opened this issue Mar 28, 2022 · 1 comment

Comments

@utybo
Copy link
Owner

utybo commented Mar 28, 2022

Thankfully, because Shedinja's internals are "open" by design and easy to mess around with, testing them is also pretty simple. It just needs to be done.

Module Priority Why ?
shedinja High Core classes need to be tested to ensure that their behavior does not shift too much in the future.
shedinja-test High shedinja-test is a very important brick of any Shedinja application and should be tested as such.
shedinja-services Medium Although important, services are usually pretty easy to debug and straightforward. Testing is important but not as much as others.
shedinja-koin-* Low Koin support is a hack upon a hack. It is quintessentially unreliable and hacky, and cannot be reliably tested.
@utybo
Copy link
Owner Author

utybo commented Apr 1, 2022

Fixed by #22

@utybo utybo closed this as completed Apr 1, 2022
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

1 participant