Quantcast

User Acceptance Test Cases For Ecommerce 14.12

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

User Acceptance Test Cases For Ecommerce 14.12

Rishi Solanki
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Rishi Solanki
Please use this link to access the mentioned page in original email -
Ecommerce-14.12
<https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12>

Thanks!

--
Rishi Solanki
Sr. Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Sat, Jan 21, 2017 at 9:21 PM, Rishi Solanki <[hidden email]>
wrote:

> 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
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Jacques Le Roux
Administrator
In reply to this post by Rishi Solanki
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
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Rishi Solanki
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 <
[hidden email]> 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
>>
>>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Jacques Le Roux
Administrator
Thanks Rishi,

Indeed I needed a clarification, sorry for that.

It's a great initiative, OFBiz will then really be at professional standards, and that's great!

I agree that we have first to create and document these UAT and then think about a tool to run them.
Cucumber seems the best tool for that to me.  I also know that Gil (Portenseigne) from Néréide has begun to use Cucumber for a custom project, hence
my haste :)

Jacques


Le 23/01/2017 à 08:05, Rishi Solanki a écrit :

> 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 <
> [hidden email]> 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
>>>
>>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Rishi Solanki
Folks,

Added two more UAT as Category Navigation and Product Search
<https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
observe some scope of improvements like UAT writing aren't following common
patterns, I'll review and fix them soon.

Soon we would add remaining in the ecommerce area, looking for your
feedback and suggestions on it.


Rishi Solanki
Sr. Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
[hidden email]> wrote:

> Thanks Rishi,
>
> Indeed I needed a clarification, sorry for that.
>
> It's a great initiative, OFBiz will then really be at professional
> standards, and that's great!
>
> I agree that we have first to create and document these UAT and then think
> about a tool to run them.
> Cucumber seems the best tool for that to me.  I also know that Gil
> (Portenseigne) from Néréide has begun to use Cucumber for a custom project,
> hence my haste :)
>
> Jacques
>
>
>
> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
>
>> 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 <
>> [hidden email]> 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
>>>>
>>>>
>>>>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Rishi Solanki
Folks,

We have completed the first draft of the document for the Ecommerce
Component
<https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
added UATs for all the user stories. Also we have follow the pattern to use
h4 h5 and h6 headings in the documents so that user can easily navigate to
the user story/ user acceptance test she wants.

As a first draft we tried to cover all known possible tests, but it might
be possible we missed something. We would like to get feedback from
community so that we can make it better in terms of usability, readability
and number of items we have tested.

Please review and share your feedback on each item, like language we use,
document formation, use cases we covered etc. We would try to cover them in
our next draft and improve the document. And once finalize we would start
using that pattern going forward for all such documents.

Thanks!


Rishi Solanki
Sr. Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
wrote:

> Folks,
>
> Added two more UAT as Category Navigation and Product Search
> <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
> observe some scope of improvements like UAT writing aren't following common
> patterns, I'll review and fix them soon.
>
> Soon we would add remaining in the ecommerce area, looking for your
> feedback and suggestions on it.
>
>
> Rishi Solanki
> Sr. Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Thanks Rishi,
>>
>> Indeed I needed a clarification, sorry for that.
>>
>> It's a great initiative, OFBiz will then really be at professional
>> standards, and that's great!
>>
>> I agree that we have first to create and document these UAT and then
>> think about a tool to run them.
>> Cucumber seems the best tool for that to me.  I also know that Gil
>> (Portenseigne) from Néréide has begun to use Cucumber for a custom project,
>> hence my haste :)
>>
>> Jacques
>>
>>
>>
>> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
>>
>>> 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 <
>>> [hidden email]> 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
>>>>>
>>>>>
>>>>>
>>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

taher
Great work Rishi, keep them coming!

I wonder if you can also create some selenium scripts to automate some of
these tests and add them to the wiki?

On Sat, Apr 15, 2017 at 6:30 PM, Rishi Solanki <[hidden email]>
wrote:

> Folks,
>
> We have completed the first draft of the document for the Ecommerce
> Component
> <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
> added UATs for all the user stories. Also we have follow the pattern to use
> h4 h5 and h6 headings in the documents so that user can easily navigate to
> the user story/ user acceptance test she wants.
>
> As a first draft we tried to cover all known possible tests, but it might
> be possible we missed something. We would like to get feedback from
> community so that we can make it better in terms of usability, readability
> and number of items we have tested.
>
> Please review and share your feedback on each item, like language we use,
> document formation, use cases we covered etc. We would try to cover them in
> our next draft and improve the document. And once finalize we would start
> using that pattern going forward for all such documents.
>
> Thanks!
>
>
> Rishi Solanki
> Sr. Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
> wrote:
>
> > Folks,
> >
> > Added two more UAT as Category Navigation and Product Search
> > <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
> > observe some scope of improvements like UAT writing aren't following
> common
> > patterns, I'll review and fix them soon.
> >
> > Soon we would add remaining in the ecommerce area, looking for your
> > feedback and suggestions on it.
> >
> >
> > Rishi Solanki
> > Sr. Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> >
> > On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
> > [hidden email]> wrote:
> >
> >> Thanks Rishi,
> >>
> >> Indeed I needed a clarification, sorry for that.
> >>
> >> It's a great initiative, OFBiz will then really be at professional
> >> standards, and that's great!
> >>
> >> I agree that we have first to create and document these UAT and then
> >> think about a tool to run them.
> >> Cucumber seems the best tool for that to me.  I also know that Gil
> >> (Portenseigne) from Néréide has begun to use Cucumber for a custom
> project,
> >> hence my haste :)
> >>
> >> Jacques
> >>
> >>
> >>
> >> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
> >>
> >>> 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 <
> >>> [hidden email]> 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
> >>>>>
> >>>>>
> >>>>>
> >>
> >
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Rishi Solanki
Thanks Taher,

Yes Jacques also push the similar idea in this thread, and we do agree with
him to add automated tests to run them frequently. Adding UATs requires
focus on the process with passion. Again I do agree here to add the
selenium, soon we would try to plan this effort.


Thanks again, Community please review and share your feedback so that we
can improve and follow the practice in all other component documents.



Rishi Solanki
Sr. Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Sat, Apr 15, 2017 at 9:22 PM, Taher Alkhateeb <[hidden email]
> wrote:

> Great work Rishi, keep them coming!
>
> I wonder if you can also create some selenium scripts to automate some of
> these tests and add them to the wiki?
>
> On Sat, Apr 15, 2017 at 6:30 PM, Rishi Solanki <[hidden email]>
> wrote:
>
> > Folks,
> >
> > We have completed the first draft of the document for the Ecommerce
> > Component
> > <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
> > added UATs for all the user stories. Also we have follow the pattern to
> use
> > h4 h5 and h6 headings in the documents so that user can easily navigate
> to
> > the user story/ user acceptance test she wants.
> >
> > As a first draft we tried to cover all known possible tests, but it might
> > be possible we missed something. We would like to get feedback from
> > community so that we can make it better in terms of usability,
> readability
> > and number of items we have tested.
> >
> > Please review and share your feedback on each item, like language we use,
> > document formation, use cases we covered etc. We would try to cover them
> in
> > our next draft and improve the document. And once finalize we would start
> > using that pattern going forward for all such documents.
> >
> > Thanks!
> >
> >
> > Rishi Solanki
> > Sr. Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> >
> > On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
> > wrote:
> >
> > > Folks,
> > >
> > > Added two more UAT as Category Navigation and Product Search
> > > <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
> > > observe some scope of improvements like UAT writing aren't following
> > common
> > > patterns, I'll review and fix them soon.
> > >
> > > Soon we would add remaining in the ecommerce area, looking for your
> > > feedback and suggestions on it.
> > >
> > >
> > > Rishi Solanki
> > > Sr. Manager, Enterprise Software Development
> > > HotWax Systems Pvt. Ltd.
> > > Direct: +91-9893287847
> > > http://www.hotwaxsystems.com
> > >
> > > On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
> > > [hidden email]> wrote:
> > >
> > >> Thanks Rishi,
> > >>
> > >> Indeed I needed a clarification, sorry for that.
> > >>
> > >> It's a great initiative, OFBiz will then really be at professional
> > >> standards, and that's great!
> > >>
> > >> I agree that we have first to create and document these UAT and then
> > >> think about a tool to run them.
> > >> Cucumber seems the best tool for that to me.  I also know that Gil
> > >> (Portenseigne) from Néréide has begun to use Cucumber for a custom
> > project,
> > >> hence my haste :)
> > >>
> > >> Jacques
> > >>
> > >>
> > >>
> > >> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
> > >>
> > >>> 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 <
> > >>> [hidden email]> 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
> > >>>>>
> > >>>>>
> > >>>>>
> > >>
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Swapnil Mane
In reply to this post by Rishi Solanki
Super, good job Rishi and team! :)


- Best Regards,
Swapnil M Mane

On Sat, Apr 15, 2017 at 9:00 PM, Rishi Solanki <[hidden email]>
wrote:

> Folks,
>
> We have completed the first draft of the document for the Ecommerce
> Component
> <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
> added UATs for all the user stories. Also we have follow the pattern to use
> h4 h5 and h6 headings in the documents so that user can easily navigate to
> the user story/ user acceptance test she wants.
>
> As a first draft we tried to cover all known possible tests, but it might
> be possible we missed something. We would like to get feedback from
> community so that we can make it better in terms of usability, readability
> and number of items we have tested.
>
> Please review and share your feedback on each item, like language we use,
> document formation, use cases we covered etc. We would try to cover them in
> our next draft and improve the document. And once finalize we would start
> using that pattern going forward for all such documents.
>
> Thanks!
>
>
> Rishi Solanki
> Sr. Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
> wrote:
>
> > Folks,
> >
> > Added two more UAT as Category Navigation and Product Search
> > <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
> > observe some scope of improvements like UAT writing aren't following
> common
> > patterns, I'll review and fix them soon.
> >
> > Soon we would add remaining in the ecommerce area, looking for your
> > feedback and suggestions on it.
> >
> >
> > Rishi Solanki
> > Sr. Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> >
> > On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
> > [hidden email]> wrote:
> >
> >> Thanks Rishi,
> >>
> >> Indeed I needed a clarification, sorry for that.
> >>
> >> It's a great initiative, OFBiz will then really be at professional
> >> standards, and that's great!
> >>
> >> I agree that we have first to create and document these UAT and then
> >> think about a tool to run them.
> >> Cucumber seems the best tool for that to me.  I also know that Gil
> >> (Portenseigne) from Néréide has begun to use Cucumber for a custom
> project,
> >> hence my haste :)
> >>
> >> Jacques
> >>
> >>
> >>
> >> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
> >>
> >>> 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 <
> >>> [hidden email]> 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
> >>>>>
> >>>>>
> >>>>>
> >>
> >
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Jacques Le Roux
Administrator
In reply to this post by Rishi Solanki
Yes it seems combining Selenium with Cucumber would not be only profitable for the OFBiz project but also for OFBiz users.

And thanks to users feedback, because it's easier to user Cucumber, than a tool like JUnit, even more profitable for the OFBiz project :)

This does not mean that JUnit is not a tool of choice, but rather for unit and integration tests. Cucumber is more users oriented.

Jacques


Le 17/04/2017 à 10:19, Rishi Solanki a écrit :

> Thanks Taher,
>
> Yes Jacques also push the similar idea in this thread, and we do agree with
> him to add automated tests to run them frequently. Adding UATs requires
> focus on the process with passion. Again I do agree here to add the
> selenium, soon we would try to plan this effort.
>
>
> Thanks again, Community please review and share your feedback so that we
> can improve and follow the practice in all other component documents.
>
>
>
> Rishi Solanki
> Sr. Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Sat, Apr 15, 2017 at 9:22 PM, Taher Alkhateeb <[hidden email]
>> wrote:
>> Great work Rishi, keep them coming!
>>
>> I wonder if you can also create some selenium scripts to automate some of
>> these tests and add them to the wiki?
>>
>> On Sat, Apr 15, 2017 at 6:30 PM, Rishi Solanki <[hidden email]>
>> wrote:
>>
>>> Folks,
>>>
>>> We have completed the first draft of the document for the Ecommerce
>>> Component
>>> <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
>>> added UATs for all the user stories. Also we have follow the pattern to
>> use
>>> h4 h5 and h6 headings in the documents so that user can easily navigate
>> to
>>> the user story/ user acceptance test she wants.
>>>
>>> As a first draft we tried to cover all known possible tests, but it might
>>> be possible we missed something. We would like to get feedback from
>>> community so that we can make it better in terms of usability,
>> readability
>>> and number of items we have tested.
>>>
>>> Please review and share your feedback on each item, like language we use,
>>> document formation, use cases we covered etc. We would try to cover them
>> in
>>> our next draft and improve the document. And once finalize we would start
>>> using that pattern going forward for all such documents.
>>>
>>> Thanks!
>>>
>>>
>>> Rishi Solanki
>>> Sr. Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: +91-9893287847
>>> http://www.hotwaxsystems.com
>>>
>>> On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
>>> wrote:
>>>
>>>> Folks,
>>>>
>>>> Added two more UAT as Category Navigation and Product Search
>>>> <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
>>>> observe some scope of improvements like UAT writing aren't following
>>> common
>>>> patterns, I'll review and fix them soon.
>>>>
>>>> Soon we would add remaining in the ecommerce area, looking for your
>>>> feedback and suggestions on it.
>>>>
>>>>
>>>> Rishi Solanki
>>>> Sr. Manager, Enterprise Software Development
>>>> HotWax Systems Pvt. Ltd.
>>>> Direct: +91-9893287847
>>>> http://www.hotwaxsystems.com
>>>>
>>>> On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
>>>> [hidden email]> wrote:
>>>>
>>>>> Thanks Rishi,
>>>>>
>>>>> Indeed I needed a clarification, sorry for that.
>>>>>
>>>>> It's a great initiative, OFBiz will then really be at professional
>>>>> standards, and that's great!
>>>>>
>>>>> I agree that we have first to create and document these UAT and then
>>>>> think about a tool to run them.
>>>>> Cucumber seems the best tool for that to me.  I also know that Gil
>>>>> (Portenseigne) from Néréide has begun to use Cucumber for a custom
>>> project,
>>>>> hence my haste :)
>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>>
>>>>> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
>>>>>
>>>>>> 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 <
>>>>>> [hidden email]> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Jacques Le Roux
Administrator
In reply to this post by Swapnil Mane
I had a cursory look, and I like it too. I guess the effort will be continued on other branches based on this one. Then later hopefully used by
Selenium tests and possibly Cucumber put in.

BTW for stable (R16.11) and trunk we have currently few issues with the logout links: see OFBIZ-9240

Thanks

Jacques


Le 17/04/2017 à 10:23, Swapnil Mane a écrit :

> Super, good job Rishi and team! :)
>
>
> - Best Regards,
> Swapnil M Mane
>
> On Sat, Apr 15, 2017 at 9:00 PM, Rishi Solanki <[hidden email]>
> wrote:
>
>> Folks,
>>
>> We have completed the first draft of the document for the Ecommerce
>> Component
>> <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
>> added UATs for all the user stories. Also we have follow the pattern to use
>> h4 h5 and h6 headings in the documents so that user can easily navigate to
>> the user story/ user acceptance test she wants.
>>
>> As a first draft we tried to cover all known possible tests, but it might
>> be possible we missed something. We would like to get feedback from
>> community so that we can make it better in terms of usability, readability
>> and number of items we have tested.
>>
>> Please review and share your feedback on each item, like language we use,
>> document formation, use cases we covered etc. We would try to cover them in
>> our next draft and improve the document. And once finalize we would start
>> using that pattern going forward for all such documents.
>>
>> Thanks!
>>
>>
>> Rishi Solanki
>> Sr. Manager, Enterprise Software Development
>> HotWax Systems Pvt. Ltd.
>> Direct: +91-9893287847
>> http://www.hotwaxsystems.com
>>
>> On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
>> wrote:
>>
>>> Folks,
>>>
>>> Added two more UAT as Category Navigation and Product Search
>>> <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
>>> observe some scope of improvements like UAT writing aren't following
>> common
>>> patterns, I'll review and fix them soon.
>>>
>>> Soon we would add remaining in the ecommerce area, looking for your
>>> feedback and suggestions on it.
>>>
>>>
>>> Rishi Solanki
>>> Sr. Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: +91-9893287847
>>> http://www.hotwaxsystems.com
>>>
>>> On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
>>> [hidden email]> wrote:
>>>
>>>> Thanks Rishi,
>>>>
>>>> Indeed I needed a clarification, sorry for that.
>>>>
>>>> It's a great initiative, OFBiz will then really be at professional
>>>> standards, and that's great!
>>>>
>>>> I agree that we have first to create and document these UAT and then
>>>> think about a tool to run them.
>>>> Cucumber seems the best tool for that to me.  I also know that Gil
>>>> (Portenseigne) from Néréide has begun to use Cucumber for a custom
>> project,
>>>> hence my haste :)
>>>>
>>>> Jacques
>>>>
>>>>
>>>>
>>>> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
>>>>
>>>>> 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 <
>>>>> [hidden email]> 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
>>>>>>>
>>>>>>>
>>>>>>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Shubham Agrawal
Superb Work Rishi and Team ;)

*Thanks and Regards,*
*Shubham Agrawal*
*Enterprise Software Engineer*
*Hotwax Systems Pvt Ltd*

On Tue, Apr 18, 2017 at 4:42 PM, Jacques Le Roux <
[hidden email]> wrote:

> I had a cursory look, and I like it too. I guess the effort will be
> continued on other branches based on this one. Then later hopefully used by
> Selenium tests and possibly Cucumber put in.
>
> BTW for stable (R16.11) and trunk we have currently few issues with the
> logout links: see OFBIZ-9240
>
> Thanks
>
> Jacques
>
>
>
> Le 17/04/2017 à 10:23, Swapnil Mane a écrit :
>
>> Super, good job Rishi and team! :)
>>
>>
>> - Best Regards,
>> Swapnil M Mane
>>
>> On Sat, Apr 15, 2017 at 9:00 PM, Rishi Solanki <[hidden email]>
>> wrote:
>>
>> Folks,
>>>
>>> We have completed the first draft of the document for the Ecommerce
>>> Component
>>> <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
>>> added UATs for all the user stories. Also we have follow the pattern to
>>> use
>>> h4 h5 and h6 headings in the documents so that user can easily navigate
>>> to
>>> the user story/ user acceptance test she wants.
>>>
>>> As a first draft we tried to cover all known possible tests, but it might
>>> be possible we missed something. We would like to get feedback from
>>> community so that we can make it better in terms of usability,
>>> readability
>>> and number of items we have tested.
>>>
>>> Please review and share your feedback on each item, like language we use,
>>> document formation, use cases we covered etc. We would try to cover them
>>> in
>>> our next draft and improve the document. And once finalize we would start
>>> using that pattern going forward for all such documents.
>>>
>>> Thanks!
>>>
>>>
>>> Rishi Solanki
>>> Sr. Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: +91-9893287847
>>> http://www.hotwaxsystems.com
>>>
>>> On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
>>> wrote:
>>>
>>> Folks,
>>>>
>>>> Added two more UAT as Category Navigation and Product Search
>>>> <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
>>>> observe some scope of improvements like UAT writing aren't following
>>>>
>>> common
>>>
>>>> patterns, I'll review and fix them soon.
>>>>
>>>> Soon we would add remaining in the ecommerce area, looking for your
>>>> feedback and suggestions on it.
>>>>
>>>>
>>>> Rishi Solanki
>>>> Sr. Manager, Enterprise Software Development
>>>> HotWax Systems Pvt. Ltd.
>>>> Direct: +91-9893287847
>>>> http://www.hotwaxsystems.com
>>>>
>>>> On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
>>>> [hidden email]> wrote:
>>>>
>>>> Thanks Rishi,
>>>>>
>>>>> Indeed I needed a clarification, sorry for that.
>>>>>
>>>>> It's a great initiative, OFBiz will then really be at professional
>>>>> standards, and that's great!
>>>>>
>>>>> I agree that we have first to create and document these UAT and then
>>>>> think about a tool to run them.
>>>>> Cucumber seems the best tool for that to me.  I also know that Gil
>>>>> (Portenseigne) from Néréide has begun to use Cucumber for a custom
>>>>>
>>>> project,
>>>
>>>> hence my haste :)
>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>>
>>>>> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
>>>>>
>>>>> 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 <
>>>>>> [hidden email]> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Paul Foxworthy
In reply to this post by Jacques Le Roux
Hi all,

I suggest Spock rather than Cucumber. It's a Groovy-based DSL. See
http://ytheohar.blogspot.com.au/2015/07/bdd-with-cucumber-vs-spock.html for
a discussion of differences between the two.

Cheers

Paul Foxworthy


On 18 April 2017 at 21:12, Jacques Le Roux <[hidden email]>
wrote:

> I had a cursory look, and I like it too. I guess the effort will be
> continued on other branches based on this one. Then later hopefully used by
> Selenium tests and possibly Cucumber put in.
>
> BTW for stable (R16.11) and trunk we have currently few issues with the
> logout links: see OFBIZ-9240
>
> Thanks
>
> Jacques
>
>
>
> Le 17/04/2017 à 10:23, Swapnil Mane a écrit :
>
>> Super, good job Rishi and team! :)
>>
>>
>> - Best Regards,
>> Swapnil M Mane
>>
>> On Sat, Apr 15, 2017 at 9:00 PM, Rishi Solanki <[hidden email]>
>> wrote:
>>
>> Folks,
>>>
>>> We have completed the first draft of the document for the Ecommerce
>>> Component
>>> <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
>>> added UATs for all the user stories. Also we have follow the pattern to
>>> use
>>> h4 h5 and h6 headings in the documents so that user can easily navigate
>>> to
>>> the user story/ user acceptance test she wants.
>>>
>>> As a first draft we tried to cover all known possible tests, but it might
>>> be possible we missed something. We would like to get feedback from
>>> community so that we can make it better in terms of usability,
>>> readability
>>> and number of items we have tested.
>>>
>>> Please review and share your feedback on each item, like language we use,
>>> document formation, use cases we covered etc. We would try to cover them
>>> in
>>> our next draft and improve the document. And once finalize we would start
>>> using that pattern going forward for all such documents.
>>>
>>> Thanks!
>>>
>>>
>>> Rishi Solanki
>>> Sr. Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: +91-9893287847
>>> http://www.hotwaxsystems.com
>>>
>>> On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
>>> wrote:
>>>
>>> Folks,
>>>>
>>>> Added two more UAT as Category Navigation and Product Search
>>>> <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
>>>> observe some scope of improvements like UAT writing aren't following
>>>>
>>> common
>>>
>>>> patterns, I'll review and fix them soon.
>>>>
>>>> Soon we would add remaining in the ecommerce area, looking for your
>>>> feedback and suggestions on it.
>>>>
>>>>
>>>> Rishi Solanki
>>>> Sr. Manager, Enterprise Software Development
>>>> HotWax Systems Pvt. Ltd.
>>>> Direct: +91-9893287847
>>>> http://www.hotwaxsystems.com
>>>>
>>>> On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
>>>> [hidden email]> wrote:
>>>>
>>>> Thanks Rishi,
>>>>>
>>>>> Indeed I needed a clarification, sorry for that.
>>>>>
>>>>> It's a great initiative, OFBiz will then really be at professional
>>>>> standards, and that's great!
>>>>>
>>>>> I agree that we have first to create and document these UAT and then
>>>>> think about a tool to run them.
>>>>> Cucumber seems the best tool for that to me.  I also know that Gil
>>>>> (Portenseigne) from Néréide has begun to use Cucumber for a custom
>>>>>
>>>> project,
>>>
>>>> hence my haste :)
>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>>
>>>>> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
>>>>>
>>>>> 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 <
>>>>>> [hidden email]> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>


--
Coherent Software Australia Pty Ltd
PO Box 2773
Cheltenham Vic 3192
Australia

Phone: +61 3 9585 6788
Web: http://www.coherentsoftware.com.au/
Email: [hidden email]
--
Coherent Software Australia Pty Ltd
http://www.coherentsoftware.com.au/

Bonsai ERP, the all-inclusive ERP system
http://www.bonsaierp.com.au/
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: User Acceptance Test Cases For Ecommerce 14.12

Jacques Le Roux
Administrator
Thanks Paul,

After a cursory review of the results of https://www.google.com/search?q=Cucumber+vs+Spock&ie=UTF-8 I tend to agree

Jacques


Le 04/05/2017 à 06:39, Paul Foxworthy a écrit :

> Hi all,
>
> I suggest Spock rather than Cucumber. It's a Groovy-based DSL. See
> http://ytheohar.blogspot.com.au/2015/07/bdd-with-cucumber-vs-spock.html for
> a discussion of differences between the two.
>
> Cheers
>
> Paul Foxworthy
>
>
> On 18 April 2017 at 21:12, Jacques Le Roux <[hidden email]>
> wrote:
>
>> I had a cursory look, and I like it too. I guess the effort will be
>> continued on other branches based on this one. Then later hopefully used by
>> Selenium tests and possibly Cucumber put in.
>>
>> BTW for stable (R16.11) and trunk we have currently few issues with the
>> logout links: see OFBIZ-9240
>>
>> Thanks
>>
>> Jacques
>>
>>
>>
>> Le 17/04/2017 à 10:23, Swapnil Mane a écrit :
>>
>>> Super, good job Rishi and team! :)
>>>
>>>
>>> - Best Regards,
>>> Swapnil M Mane
>>>
>>> On Sat, Apr 15, 2017 at 9:00 PM, Rishi Solanki <[hidden email]>
>>> wrote:
>>>
>>> Folks,
>>>> We have completed the first draft of the document for the Ecommerce
>>>> Component
>>>> <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce+14.12> and
>>>> added UATs for all the user stories. Also we have follow the pattern to
>>>> use
>>>> h4 h5 and h6 headings in the documents so that user can easily navigate
>>>> to
>>>> the user story/ user acceptance test she wants.
>>>>
>>>> As a first draft we tried to cover all known possible tests, but it might
>>>> be possible we missed something. We would like to get feedback from
>>>> community so that we can make it better in terms of usability,
>>>> readability
>>>> and number of items we have tested.
>>>>
>>>> Please review and share your feedback on each item, like language we use,
>>>> document formation, use cases we covered etc. We would try to cover them
>>>> in
>>>> our next draft and improve the document. And once finalize we would start
>>>> using that pattern going forward for all such documents.
>>>>
>>>> Thanks!
>>>>
>>>>
>>>> Rishi Solanki
>>>> Sr. Manager, Enterprise Software Development
>>>> HotWax Systems Pvt. Ltd.
>>>> Direct: +91-9893287847
>>>> http://www.hotwaxsystems.com
>>>>
>>>> On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki <[hidden email]>
>>>> wrote:
>>>>
>>>> Folks,
>>>>> Added two more UAT as Category Navigation and Product Search
>>>>> <https://cwiki.apache.org/confluence/display/OFBIZ/Ecommerce+14.12>. I
>>>>> observe some scope of improvements like UAT writing aren't following
>>>>>
>>>> common
>>>>
>>>>> patterns, I'll review and fix them soon.
>>>>>
>>>>> Soon we would add remaining in the ecommerce area, looking for your
>>>>> feedback and suggestions on it.
>>>>>
>>>>>
>>>>> Rishi Solanki
>>>>> Sr. Manager, Enterprise Software Development
>>>>> HotWax Systems Pvt. Ltd.
>>>>> Direct: +91-9893287847
>>>>> http://www.hotwaxsystems.com
>>>>>
>>>>> On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
>>>>> [hidden email]> wrote:
>>>>>
>>>>> Thanks Rishi,
>>>>>> Indeed I needed a clarification, sorry for that.
>>>>>>
>>>>>> It's a great initiative, OFBiz will then really be at professional
>>>>>> standards, and that's great!
>>>>>>
>>>>>> I agree that we have first to create and document these UAT and then
>>>>>> think about a tool to run them.
>>>>>> Cucumber seems the best tool for that to me.  I also know that Gil
>>>>>> (Portenseigne) from Néréide has begun to use Cucumber for a custom
>>>>>>
>>>>> project,
>>>>> hence my haste :)
>>>>>> Jacques
>>>>>>
>>>>>>
>>>>>>
>>>>>> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
>>>>>>
>>>>>> 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 <
>>>>>>> [hidden email]> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>

Loading...