please ensure to share the entire logs in a text readable format
I had used pastebin for the error here C:\Users\Insookwa\openmrs\openmrs-contrib-qaframework>mvn clean testJava Hot - Pastebin.com it also here in text form
C:\Users\Insookwa\openmrs\openmrs-contrib-qaframework>mvn clean install
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------< org.openmrs.contrib:qaframework >-------------------
[INFO] Building OpenMRS QA Framework 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ qaframework ---
[INFO] Deleting C:\Users\Insookwa\openmrs\openmrs-contrib-qaframework\target
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.710 s
[INFO] Finished at: 2020-10-09T13:50:09+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project qaframework: Failed to clean project: Failed to delete C:\Users\Insookwa\openmrs\openmrs-contrib-qaframework\target\chromedriverlogs\chromedriver-ConditionsSteps.log -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Thanks for everyone who has been testing both manual and writing integration tests in qa-contrib. cc @k.joseph there seem to be some integration tests in review mode, kindly take a look thanks ,some members seems blocked
We can consider these as refs for this Sprint.
cc @achilep @insookwa thanks for working on automation tests, is there any further progress, kindly share any thing or blocker such that we can track the progress thanks
2 Likes
if we can have some comment on this PR your project isn’t cleaning, run with -X option for details, try mvn clean -X
1 Like
@sharif, There is a problem with time zones when it comes to managing appointments. Could it be having issues with the ref app version or it will be rectified before the release?
1 Like
Can you share the screen shot of your testing with managing appointments, we need to also test it together and confirm thanks. ohh true dat!!! so that message means you need to set your computer to a timezone that caters the appointments. thats very ok
1 Like
i have just edited the post with the attachment
1 Like
I’ve not always got this message but when starting a visit, I’ve realised the time is always wrong from my computer. probably its time zones issue
1 Like
Hi All , i would like to thank Everyone who has taken part in this 14 day Testing sprint ahead of Refapp 2.11.0 Realease . Thanks to @insookwa @achilep @gracebish @sharif for work well done / still doing on both Manual and writing Automated tests.
Thanks to @k.joseph for setting up the tasks on JIRA
Alot of work has been accomplished , but a mountain still awaits us.
As we come to the close of this sprint , I would like to invite all of you to attend the Retrospective on Monday 19th 2020 immediately after PM call so we can resolve the remaining issues.
If all goes well , we have a bunch of other issues to solve and we hope to wrap them in a different sprint , i would therefore implore you all to join the call on Monday so we can get this done.
I would like to ask @grace to add this on the OpenMRS calender.
Regards Tendo
2 Likes
Thanks @tendomart for leading this, Do we have any new tests that we have accomplished in this first testing? Otherwise thanks everyone
Yes there are a couple of tests on JIRA pending approval , so we want to know the status by Monday.
2 Likes
@sharif @tendomart & others - please see our new shared Board for the RefApp 2.11 release work: https://issues.openmrs.org/secure/RapidBoard.jspa?rapidView=236&view=planning
The board pulls from the list of tickets that have “Fix Version: Reference Application 2.11.0” attached to them, regardless of the project they are in.
Today we had a backlog grooming session and identified the top 4 priority tickets as a first example. I’ve added the 4 tickets we reviewed today to Sprint 2 as an example:
Next Steps
- Finishing Sprint Planning: We obviously don’t want to put all 80+ tickets into Sprint 2
However we probably want a few more than are currently there. @sharif @tendomart and others in this thread, would you like to review the backlog and add high-priority tickets into Sprint 2? - @tendomart or @sharif would you kick-off Sprint 2 by clicking “start sprint” in the board, and making the Talk announcement? Is that how you’d like to proceed?
1 Like
Hey @insookwa I saw you did test number 3, testing on a tablet. I found a funny issue using my tablet for the attachments functionality. It seems using the tablet workflow makes people fat. 
No, not really, but it seems like pictures I take using the take-picture button in OpenMRS on my tablet cause the picture to stretch horizontally - but this is not an issue on my tablet in other apps, and the image is fine if I use my desktop to take the picture or upload a picture.
See the one on the far right here (which I took with my tablet in the Attachments workflow) is stretched. If you have a tablet can you see if you can replicate this? Not a top priority or anything, would just be nice to know if we would need to fix this. I joke but you wouldn’t want to distort a visual image of a patient, especially if it’s important to see how someone’s face or wound changes shape over time.
Question for @achilep - I see you recorded this:
Good catch re. the general actions list being empty, that confused me at first as well. Do you know, is it supposed to be empty? Is there a bug for this?
2 Likes