Closed joiskash closed 1 year ago
How exactly is the "click" supposed to be unit-tested? If it were an instrumentation test then we could verify the nature of click via seeing if the corresponding dropdown occurs or not, but how is it going to be unit tested? Can you please throw some light on it, it would be very kind of you, thanks
Thanks @s-ayush2903. I've updated the title of the issue. Will you be interested in taking this issue?
Yes, definitely. But I have a question, our automated testing architecture would be a/c to what, I mean we would be using espresso or UI automator along with robot pattern?
Yes I think we would be using espresso and/or UI automator. Will you be able to do some research and create a draft PR please?
Yes
@jingtang10 Should I create the PR asap or wait for #294 to be merged, as if it gets merged in the middle of the test PR, then there'll be a lot of conflicts in the testing PR.
Please don't wait as that PR hasn't been approved yet. Also it's only a reformatting PR so although it will cause conflicts it should be easy to resolve. If you're rebasing please just make sure that you're using the version on your own branch and ignore the master's HEAD. that way the only thing you have to do after rebasing is to rerun ./gradlew spotlessApply
. I hope this makes sense.
is there more progress on this? thanks!
Moving it up in my list :+1:
"click" event has to be tested for widgets like the date picker, drop down etc.
more work to address these issues in the first comment.
we need to test the click event for the date picker and date time picker still.
@jingtang10 I would like to work on 2 remaining tasks of https://github.com/google/android-fhir/issues/107. Can you please assign it to me?
Sorry. That issue is obsolete.
Ok @jingtang10 , Sir can you please assign me this issue?
@Tarun-Bhardwaj hey is this issue still valid?
Just cleaning things up. Closing this as our androidTests inclide clicking
"click" event has to be tested for widgets like the date picker, drop down etc.