Hi James, ... alright... noted. A bit new to the release game here so the requirement to manually test slipped through the cracks. But maybe August might also not be the best of months for a release; responses to the various release announcements on the mailing list were a bit scarce.
Having said that: someone wants to help out with QA as James mentioned? I'll give it a run on my machine, but would be great if we get a couple more people to verify. Speaking of manual testing - maybe we could do this a bit less manual... I wanted to propose this already for a while and didn't get to it: https://gatling.io/ So technically Gatling is a load testing tool, but it has a feature called Gatling Recorder (https://gatling.io/docs/current/http/recorder/) that allows you to record all interaction between browser (read: community app) and Fineract. That way we could get those test scenarios once recorded and just include them in the build as some kind of integration test. The beauty of this is that maintenance doesn't require any coding, just run a specific scenario again in your browser; could even replace the current integration tests in Fineract that should - I guess - cover more or less UI scenarios, but are currently a bit neglected. Please ping here on the list if you want to help out. We can coordinate then for the final release date (I guess that won't be Monday). Thanks again for the help James. Cheers, Aleks On Fri, Aug 21, 2020 at 7:20 PM James Dailey <[email protected]> wrote: > Alex, > > I would like to see and understand the steps we need to take w regard to > quality assurance (QA). It is vital that we have enough test coverage. If > we don't have that, then we may need to hold off on the release until we > do. > > In previous releases we always relied heavily on users going through each > user interface screen to identify bugs. There were even bug finding > rewards. This was true for the decade + that the code lived as Mifos. > > Since the Mifos front end UIs (multiple) are not yet at the same > development state, I believe we need to make sure that test coverage is > adequate at the unit level and end to end level. > > Perhaps other devs could tell is what has been done to ensure the QA is > there. > > If there are additional testing needs, let's also make sure we have jira > tickets for those. > > If the Mifos UIs on the Mifos dev branches are tracking w this 1.4 release > exactly, then perhaps that can be used for the testing here. > > QA should also include a look at any security issues that were solved. > > Thanks, > > @jdailey > > On Fri, Aug 21, 2020, 5:42 AM Aleksandar Vidakovic < > [email protected]> wrote: > >> Hi Everyone, >> >> As previously announced, I've just created the release branch for our >> upcoming 1.4.0 release. >> >> You can continue working and merging PRs to the develop branch for future >> releases, as always. >> >> The DRAFT release notes are on >> https://cwiki.apache.org/confluence/display/FINERACT/1.4.0+-+Apache+Fineract. >> Does anyone see anything missing? >> >> Does anyone have any last minute changes they would like to see >> cherry-picked to branch 1.4.0, or are we good to go and actually cut the >> release based on this branch as it is? >> >> I'll start the final stage of actually creating the release in 3 days >> (Monday, August 24) if nobody objects. >> >> Cheers, >> >> Aleks >> >>
