This repository has been archived by the owner on Nov 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 109
Cover components with unit tests #1
Labels
help wanted
Extra attention is needed
Comments
TejasQ
added
help wanted
Extra attention is needed
good first issue
Good for newcomers
labels
Jul 2, 2018
I can take this on! |
Do it! 💪 |
@Xiot, still interested to finish this? |
Sorry, I haven't had any time recently.
…On Mon, Jul 16, 2018, 11:00 AM Tejas Kumar, ***@***.***> wrote:
@Xiot <https://github.com/Xiot>, still interested to finish this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABzMVr2b3kGIYy-oHuY80GFXzaUCvFMrks5uHKp_gaJpZM4U_mTY>
.
|
Would you still like to do it? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Why
Unit tests are good and allow us to have predictable software.
What
Currently, components like Get and Poll work reliably and beautifully, but are not covered with unit tests. It would be nice if we had them covered with test in order to prevent side effects and surprises when consuming these components.
The text was updated successfully, but these errors were encountered: