Hi Sam, A useful technique is to base tests on the use cases / activity diagrams. It may be a good idea to focus on creating these first.
BOUML is a good free tool for UML diagramming. Cheers, Chris On Wed, May 26, 2010 at 7:27 AM, Sam Hamilton <[email protected]> wrote: > Hi Chris, > > Perhaps if we start with the a big overview of test cases per component > people will start adding to them later for the ones that are missing? > > Perhaps the simplest tests to start adding would be ecommerce as its all > customer facing and so in my opinion the simplest to get good selenium > coverage. > > I can help out with some facility stuff as we use that here. > > Cheers > Sam > > > On 26/05/2010 12:12, chris snow wrote: > > Hi BJ - i'd like to start adding selenium tests, however, before adding > > selenium tests, test cases need to be created. To create test cases, > process > > flows need to be understood/documented (I'm still at the understanding > stage > > hence my work on the help system). So in conclusion only those with > > detailed knowledge of ofbiz processes can start adding selenium tests > (only > > a few people?). > > > > On 26 May 2010 03:18, "BJ Freeman" <[email protected]> wrote: > > > > we need button pusher and business that need to accomplish a task. > > one of the top level testing tools is selenium > > https://issues.apache.org/jira/browse/OFBIZ-3511 > > your welcome to add to the library. > > > > ========================= > > BJ Freeman > > http://bjfreeman.elance.com > > Strategic Power Office with Supplier Automation < > > http://www.businessesnetwork.com/automation/viewforum.php?f=93> > > Specialtymarket.com <http://www.specialtymarket.com/> > > > > Systems Integrator-- Glad to Assist > > > > Chat Y! messenger: bjfr33man > > Linkedin > > < > > > http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro > >> > > > > > > Matt Warnock sent the following on 5/25/2010 6:40 PM: > >> Based on encouraging comments from you and Jacopo and others, and seeing > >> the rate at which new commits are added, I am thinking it may be best to > >> get on the trunk, even for production. However I can't imagine running > >> nightly builds on a production server. > >> > >> I'm thinking I'd build nightly on the development laptop, and update the > >> production server every week or two, to a fairly recent, more-or-less > >> "known good" revision level. I'm hoping this would provide the best of > >> both worlds. And I'm hoping that this would avoid any mission-critical > >> breakages until the fixes have been committed. Does that seem > >> reasonable? > >> > >> I don't kid myself that I can submit much code yet, but hopefully I can > >> help test and document bugs, even if I can't fix them yet. Hopefully > >> that will come soon. > >> > > > >
