Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upTests for each functionality #8
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Zhuinden
May 19, 2018
Owner
Completely agree! Lot of the code is based on agoda/kakao, but tests would be nice nonetheless
|
Completely agree! Lot of the code is based on agoda/kakao, but tests would be nice nonetheless |
Zhuinden
added
the
good first issue
label
May 25, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aumarbello
Sep 12, 2018
Interested in taking this up, but could explain the nature of the tests that should be written?
aumarbello
commented
Sep 12, 2018
|
Interested in taking this up, but could explain the nature of the tests that should be written? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Zhuinden
Sep 12, 2018
Owner
@aumarbello technically there are a bunch of assertion types that start with check___, technically this block of code
For example, for checkContainsText, you'd need a text view that has a given text, and you would need to verify that if the TextView contains the right text then there is no assertion error, but if the TextView contains the wrong text then an assertion error is thrown.
This would be required for each check___ assertion type, but just adding any of such tests would be helpful.
Evidently, this would have to be done in instrumentation test.
|
@aumarbello technically there are a bunch of assertion types that start with For example, for This would be required for each Evidently, this would have to be done in instrumentation test. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aumarbello
Sep 12, 2018
Okay, so for example if I want to test all the assertions that have to do with texts I will need an activity with TextView and in the activity's instrumentation test after using the assertions, verify the behavior (happy and sad path) of the assertions I used right?
aumarbello
commented
Sep 12, 2018
|
Okay, so for example if I want to test all the assertions that have to do with texts I will need an activity with TextView and in the activity's instrumentation test after using the assertions, verify the behavior (happy and sad path) of the assertions I used right? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Yep! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aumarbello
Sep 12, 2018
Okay, would love to work on the full suites of tests but would it be okay to do so gradually?
aumarbello
commented
Sep 12, 2018
|
Okay, would love to work on the full suites of tests but would it be okay to do so gradually? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Zhuinden
Sep 12, 2018
Owner
I mean, it'd be crazy if I expected immediate 100% completion, I'm already glad someone volunteers for any of it in the first place.
Totally ok to do it gradually, of course. Happy to have help in general.
|
I mean, it'd be crazy if I expected immediate 100% completion, I'm already glad someone volunteers for any of it in the first place. Totally ok to do it gradually, of course. Happy to have help in general. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aumarbello
commented
Sep 12, 2018
|
Okay, would get started on it. |
xgleich1 commentedMay 19, 2018
•
edited
First of all a big thanks for your work on this lib, it looks really helpful!
Bit I am hesitant to use it since there are almost no tests in this project (the simple one in the sample project is not enough) and thus no way to verify that your code works as intendet.
This would also serve as a great way to showcase your complete api.