Hi all, App Factory UI tests have been committed to [1]. The test suite covers all completed use cases mentioned in above mail threads.
UI auto tests will be skipped from regular App Factory build by default. mvn install -DskipTests=false To run the tests you have to use following command. All test configuration were set to default and you can run the test OOB with app factory staging environment. You need to change following test settings in order execute tests on different environment. 1. Edit af.host.name property in atuomation.properties file at appfactory/1.0.0/modules/integration/tests-ui/src/test/resources af.host.name=staging.appfactorypreview.wso2.com 2. To add new user, edit userList.csv file at appfactory/1.0.0/modules/integration/tests-ui/src/test/resources Currently test runs with manually created user in LDAP store. 3. To Change browser type, edit browser.name property in automation.properties file. browser.name=firefox Let us know if you find any difficulty with executing tests. Thanks, Krishantha. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/products/appfactory/1.0.0/modules/integration/tests-ui On Thu, Jun 13, 2013 at 5:16 PM, Krishantha Samaraweera <[email protected] > wrote: > Hi Randika, > > Thanks for the update. > > Lets pack completed test cases and give it to QA and Product team. So they > and run the test suite for each update. > > Thanks, > Krishantha. > > On Thu, Jun 13, 2013 at 5:07 PM, Randika Ratnayake <[email protected]>wrote: > >> HI , >> Here is an update for the UI automation of the AppFactory >> >> covered User Stories >> >> 1. Log-in to App Factory >> 2. App Factory User Home details verification of the created application >> 3. Create an Application >> 4. Edit an Application >> 5. Basic application overview details verification >> 6. view application team verification >> 7. Add member to Team. >> 8. Repository Management.(this include branching the Application ) >> 9. Governing an application (Promoting in life Cycle Stages) >> 10. Complete Application Overview Verification. >> >> Uncovered User Stories >> 1. User registration - this is a email verification process and this has >> to be done manually. >> 2. view update user profile - this feature is not yet implemented >> 3. edit an Application - only the description could be edited >> 4. Delete an Application - application deletion feature is not yet >> implemented >> 5. configure data source resources - not yet implemented. >> >> >> >> To be covered >> 1. update team >> 2. configure database resources >> 3. configure data source resources >> 4. configure API resources >> 5. configure property resources >> 6. Application development >> 7. Build Application/deploy application >> 8. test application >> >> there are few user stories which should be verified manually (Obtain >> server logs,manage issues) working on a way to work on those areas.l >> >> >> regards >> >> Randika >> >> >> >> >> >> >> >> >> >> On Mon, Jun 3, 2013 at 2:27 PM, Shiroshica Kulatilake <[email protected]>wrote: >> >>> Hi Randika, >>> >>> If that's the case - then OK ! >>> >>> A new version of the user stories has been posted to the "WIP >>> wireframe.. " email thread. >>> >>> Thank you, >>> Shiro >>> >>> >>> On Mon, Jun 3, 2013 at 2:20 PM, Randika Ratnayake <[email protected]>wrote: >>> >>>> hi Shiro, >>>> >>>> Development of this selenium tests are completely based on UI based >>>> functionality testing. one purpose of doing this is getting adhere to >>>> rapid UI change in our end. as you mentioned there would be a rework due >>>> to the UI changes, but will continue the UI automation in the Staging and >>>> tying to work out a mechanism to adhere to the UI changes >>>> Regards >>>> >>>> >>>> On Mon, Jun 3, 2013 at 2:02 PM, Shiroshica Kulatilake >>>> <[email protected]>wrote: >>>> >>>>> Hi Randika, >>>>> >>>>> I have a few questions; >>>>> >>>>> 1. Will you be doing this based on the current UI's on staging ? >>>>> 2. Would you be recording user movements ? >>>>> 3. Would there be a functionality only test set which is not dependent >>>>> on the UIs ? >>>>> >>>>> If the goal is to do this for the AF GA release there might be a bit >>>>> of rework once the new front ends come. These are supposed to be released >>>>> for QA incrementally (please see AF GA Release email thread). >>>>> >>>>> Letting you know before so that you can plan accordingly. >>>>> >>>>> Thank you, >>>>> Shiro >>>>> >>>>> >>>>> >>>>> On Mon, Jun 3, 2013 at 1:31 PM, Randika Ratnayake >>>>> <[email protected]>wrote: >>>>> >>>>>> hi all , >>>>>> >>>>>> Selenium Automation test development is started for the AppFactory >>>>>> staging . will be referring the below attached user stories for the >>>>>> automation process. please update for any missing user stories / use case >>>>>> needed to automated to this thread. >>>>>> >>>>>> Regards >>>>>> -- >>>>>> Randika Ratnayake, >>>>>> Mobile : +94773-440677 <[email protected]> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Shiroshica Kulatilake >>>>> >>>>> Architect, >>>>> WSO2, Inc. http://wso2.com/ >>>>> Phone: +94 776523867 >>>>> >>>> >>>> >>>> >>>> -- >>>> Randika Ratnayake, >>>> Mobile : +94773-440677 <[email protected]> >>>> >>> >>> >>> >>> -- >>> Shiroshica Kulatilake >>> >>> Architect, >>> WSO2, Inc. http://wso2.com/ >>> Phone: +94 776523867 >>> >> >> >> >> -- >> Randika Ratnayake, >> Mobile : +94773-440677 <[email protected]> >> > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
