android-fhir
android-fhir copied to clipboard
Add integration tests for the QuestionnaireFragment in the datacapture module
https://github.com/google/android-fhir/issues/184#issue-794091744
Are we going to follow the robot pattern for testing the activities and fragments(mostly UI testing), also what we'll use, UI automator or espresso?
try something like this to test the QuestionnaireFragment
I'll take up this issue once it is clear/finalized what to use.
oops sorry i forgot to add this link: https://developer.android.com/guide/fragments/test
@s-ayush2903 I noticed you are working on #186 . Are you working on this as well or can I take it up?
Yeah, I'm working on this too, there are so many branches now, I'll claim less issues now onwards 🥴
@jingtang10 The spelling of Questionnaire in the issue title is wrong :laughing: , change it before someone opens a PR for it 😝
@jingtang10 The spelling of Questionnaire in the issue title is wrong 😆 , change it before someone opens a PR for it 😝
😅
I didn't intend it specifically for someone, just had in my head that there were few PRs related to it :sweat_smile:. Apologies if it made you feel uneasy :disappointed:.
I didn't intend it specifically for someone, just had in my head that there were few PRs related to it 😅. Apologies if it made you feel uneasy 😞.
No relax 😂.
@s-ayush2903 I've updated the title of this issue - the QuestionnaireFragment
in question is the one in the datacapture
module rather than the datacapturegallery
module. Sorry if this wasn't clear.
Thanks for info! Then what to do with the linked PR, Probably create an issue that targets the test it proposes, thoughts?
Thanks @s-ayush2903! I don't think testing the reference (gallery) application is a priority for us. In fact, I would go as far as saying it probably is a distraction. So I really would rather not work on this for now. Can you please close the linked PR and we can revisit if this becomes a priority? Thanks
@s-ayush2903 please comment on if you want to work on this? and unassign if appropriate.
As mentioned previously in the channel I'm not able get the instrumentation tests running on my machine for libs, so I won't be able to work on any related issues.
As mentioned previously in the channel I'm not able get the instrumentation tests running on my machine for libs, so I won't be able to work on any related issues.
++ I can't get them working on my device either.
As mentioned previously in the channel I'm not able get the instrumentation tests running on my machine for libs, so I won't be able to work on any related issues.
What I found on my machine is that I have to right click the folder containing the instrumentation tests and select run... Not sure if this helps you.
As mentioned previously in the channel I'm not able get the instrumentation tests running on my machine for libs, so I won't be able to work on any related issues.
What I found on my machine is that I have to right click the folder containing the instrumentation tests and select run... Not sure if this helps you.
Thanks this works. Any idea why this happens?
As mentioned previously in the channel I'm not able get the instrumentation tests running on my machine for libs, so I won't be able to work on any related issues.
What I found on my machine is that I have to right click the folder containing the instrumentation tests and select run... Not sure if this helps you.
Thanks this works. Any idea why this happens?
I'm not sure sorry. @deepankarb @yigit @florina-muntenescu @kevinmost not sure if anyone else knows why this is happening and if this is a bug worth filing to android studio.
Thanks @s-ayush2903! I don't think testing the reference (gallery) application is a priority for us. In fact, I would go as far as saying it probably is a distraction. So I really would rather not work on this for now. Can you please close the linked PR and we can revisit if this becomes a priority? Thanks
hi @jingtang10 is this being revisited now? i saw it in-progress here : https://github.com/google/android-fhir/projects/1#column-12632674 can I work on this?
Just cleaning things up. Closing this as QuesitonnaireFragmentTest exists