It would be great to engage the QA team in testing during the sprint. Could you guys please have a look at the issues and propose the best way for the team to contribute to testing? @wyclif is the sprint leader and he should be able to assist you.
This looks very interesting. Currently we are too busy with automation tests to have a detailed look, but we surely can talk about it and decide about the best approach next Monday.
Generally, I think we should take the “standard” aproach of creating new Test Cases covering issues included in the sprint, executing them and finally creating automation Tests for each Test Case.
@pavlo, @yulia, what do you think? Perhaps you have some ideas about anything more we can do?
Mueller did mention on one of the threads about the sprint that they wanted to participate and write up some UI tests, the sprint started today (July 27th). We are glad to have you guys doing this
@pavlo, @yulia
Our latest conclusion is to follow https://issues.openmrs.org/secure/RapidBoard.jspa?rapidView=77 and verify issues that are “Ready for Test”. While testing the issue should be in “In Test” state. If it passes the test leave the issue in “Ready for Showcase” state. During testing please use the existing Test Cases if possible and rewrite it according to UI changes. Adding new test cases will only be necessary if a bug will be found that needs some more complicated set of actions to reproduce.
Yes, currently we will focus on manual testing, it is difficult to say whether there will be a need for creating new UI Tests for this Sprint.
Please wait for the tasks until https://ci.openmrs.org/browse/REFAPP-OMODDISTRO will be passing the current UI tests.