Thanks Jacques for your reply and raising concerns. It seems that, I was not clear enough. Let me try to rephrase what we are doing. If you observe then Pranay has created new hierachy for each release like 14.12, 15.12 ... so on.
For each release we have the user stories, and we are adding UATs for each user story. For each user story we are discussing the cases we should test manually and also try them to dicuss on the mailing list (user/dev). Once we are sure, we document and test the cases (manually) and put the results in the Actual results and Pass/Fail. Please note that, before documenting anything as Pass or Fail we are really running that scenario. The intention of doing this, we can say that the released branches of OFBiz are tested on certain scenarios and all get passed. After completing this activity, we as a community can say 14.12 branch tested for say 1000 user acceptance test cases and out of them 950 get passed and 50 are reported and fail for that branch. Once we complete this activity, we could start fixing them. For the same we have started multiple email threads to get the feedback from community, so that we could get more cases for the user stories. In other words, we have automated tests with us, but this time we are trying to add documents for the manual tests user could see and increase in faith on each relase. I hope I'm clear this time :-). And yes I agree on the fact that we should think on automating these tests to run them frequently. And I think for that we again need what to tests get documented. We can assume it as first step towards automation. PS: Team, please add more details if I miss something. Rishi Solanki Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com On Sun, Jan 22, 2017 at 5:00 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Thanks Rishi, > > This is interesting, do you envision a mean to automate these tests and > run them frequently? > > Say either on each build (using BuildBot for instance), or on another > frequency if they happens to be at term longer than our commit frequency > would support. > > So the question is do you plan to use a tool for that? I say that because > it seems to me that Cucumber (MIT license) could be used for that... > > Jacques > > > Le 21/01/2017 à 16:51, Rishi Solanki a écrit : > >> Devs, >> >> We have started working on few user stories mentioned at Ecommerce-14.12 >> <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12> and >> adding user acceptance test (UAT) cases for them. For now we have added >> test cases for two user stories as follows; >> - Login Page >> - Login and Update Personal Information >> >> We have updated the document with the identified UATs so that can get >> feedback from community on them. >> >> - For now we have added the UATs just below the user stories in the >> document. Please let us know if we are fine with this location? >> - We are using *EC-LP* and *EC-LUPI *as prefix for the above mentioned two >> user stories. Please review and let us know your thoughts on it, so that >> we >> can follow one common pattern. >> >> Any other feedback in UATs are most welcome to improve the quality. Going >> forward we would follow the same practice. >> >> Thanks to Aman Mishra for providing the UATs for both stories. >> >> >> Best Regards, >> -- >> Rishi Solanki >> Sr. Manager, Enterprise Software Development >> HotWax Systems Pvt. Ltd. >> Direct: +91-9893287847 >> http://www.hotwaxsystems.com >> >> >
