Replies: 1 comment 3 replies
-
Hi @piofusco, that's a great suggestion. We're all in favour of having more tests coverage 👍 If you see fit for more unit tests in particular areas, you're more than welcome to do so. At the moment we're more focused on adding coverage on new classes only since we have a lot of work in our pipeline. Keep in mind for the AppDelegate that there's currently a PR opened to move to SceneDelegate thought, so if you wanna touch that are I would suggest having a look there. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are a number of classes within the repo that do not have unit tests. For some of these classes, there are higher order tests that interact with the UI and probably cover a lot of their functionality, but there's a lot of behavior left unchecked. While I wouldn't suggest having a unit test just to check a box, I am wondering if it would be appropriate to add unit tests for more critical or complicated classes. One class that comes to mind is
AppDelegate
.Would it be appropriate for someone to backfill unit tests for some of the more involved classes? Additionally, is there any intention to increase unit testing coverage over time?
Beta Was this translation helpful? Give feedback.
All reactions