Please, all those devs who updated the UI, also update the tests. In other words, you have to consider the dev task not complete, if the automated tests are not running on the improved UI.
Thanks, Samisa... On Mon, Jan 18, 2010 at 3:40 PM, Charitha Kankanamge <[email protected]>wrote: > We have identified some of the components which are going through > significant UI changes hence the existing automated tests cannot be used > with them. > > - Registry Browser > - DS UI > - Endpoints UI > - Proxy service UI (these changes are in progress according to the dev > team) > - Sequences > - Registry services UI > - BPS UI (Are we doing this for carbon3?) > - IS Entitlement UI > - User Management (ui is completely changed) > - Are there UI changes related to multi-tenancy? > > In addition to this, there are new features which must be automated by QA. > eg:- OoAuth, SSO UI, passive STS, Handler UI, Service Configuration UI in > registry > Also, are we going to do a usability review of all products before 3.0 > release and change the UIs etc.. accordingly. If so, we must take those > changes in to consideration when updating/re-writing automated tests. > > > Regards > Charitha > > Charitha Kankanamge > WSO2 Inc. > http://wso2.org > email: [email protected] > cell: +94 718 359 265 > blog: http://charithaka.blogspot.com > > > On Fri, Jan 15, 2010 at 10:50 PM, Samisa Abeysinghe <[email protected]>wrote: > >> >> >> On Fri, Jan 15, 2010 at 10:45 PM, Charitha Kankanamge >> <[email protected]>wrote: >> >>> No automated selenium tests are not configured to trigger on nightly >>> builds. We did not find time to go through the tests and check whether they >>> can run on trunk (IIRC, recently Darshana was doing changes required to run >>> automates tests against trunk) . Ideally, we just need to point to nightly >>> build urls to make it to work however if there are significant changes in >>> UI/directory structures etc.. tests should be rewritten/updated accordingly. >>> Will check this with team ASAP. >>> >> >> Before fixing the tests, first get the tests to run with >> the nightly builds. Then we can get people to fix those that are failing. >> >> We need to do this now, or else, people will take liberties breaking the >> trunk. >> >> Also, if UIs are changing, those devs who change the UIs MUST help with >> fixing the test - we do not have enough bandwidth in QA to keep on fixing >> the broken tests. So if tests are broken, make it a habit to SHOUT. :) >> >> Samisa... >> >>> >>> Regards >>> Charitha >>> >>> Charitha Kankanamge >>> WSO2 Inc. >>> http://wso2.org >>> email: [email protected] >>> cell: +94 718 359 265 >>> blog: http://charithaka.blogspot.com >>> >>> >>> On Fri, Jan 15, 2010 at 10:33 PM, Samisa Abeysinghe <[email protected]>wrote: >>> >>>> Are we running automated tests on trunk with nightly builds? >>>> If yes: >>>> How can I run those manually on a trunk product build? >>>> If no: >>>> Why not? >>>> >>>> Thanks, >>>> Samisa... >>>> >>>> -- >>>> Samisa Abeysinghe >>>> Director, Engineering - WSO2 Inc. >>>> >>>> http://www.wso2.com/ - "lean . enterprise . middleware" >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Samisa Abeysinghe >> Director, Engineering - WSO2 Inc. >> >> http://www.wso2.com/ - "lean . enterprise . middleware" >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - "lean . enterprise . middleware"
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
