Loading ...
Sorry, an error occurred while loading the content.
 

RE: [XP] Another tools question - acceptance test frameworks this time

Expand Messages
  • Phil Lewis
    D oh wrong thread sorry ... http://docs.yahoo.com/info/terms/
    Message 1 of 8 , Feb 26, 2002
      D'oh

      wrong thread

      sorry


      > -----Original Message-----
      > From: Phil Lewis [mailto:phil.lewis@...]
      > Sent: 26 February 2002 13:10
      > To: 'extremeprogramming@yahoogroups.com'
      > Subject: RE: [XP] Another tools question - acceptance test frameworks
      > this time
      >
      >
      > another 2pth
      >
      > If are going to have 30-40 developers working who need - perhaps for
      > commercial reasons (like having a public API to large parts of a wide
      > ranging set of components) - to be working on the same
      > 'project' then how
      > about:
      >
      > Start with a team of four really good developers. Let them
      > implemet the
      > first couple of iterations. If 'architectural' issues
      > (typically things like
      > a transactioning, scaling, security etc) are important to the
      > customer, then
      > make sure a few of the selected stories include these aspects
      > explicitly.
      > But also make sure that you get some real functionality out of these
      > iterations.
      >
      > This will allow the four top developers some time to begin evolving an
      > archtectural vision.
      >
      > Next, double the team size and do a couple more iterations.
      > Make sure the
      > newcomers are not newbie developers, and make sure that at
      > least for the
      > first iteration, they pair with one of the originals. Make
      > sure you refactor
      > mercilesly, maintaining and developing the architectural vision.
      >
      > Add a few more developers, and so on. We adopted this
      > approach, and we now
      > have nearly twenty people who all feel that they each
      > individually own the
      > whole architecture.
      >
      > As for 30-40 developers per project: split them into sub
      > projects! We never
      > have more than 10 people on a team (normally fewer), usually
      > with each team
      > working on its own project.
      >
      > If you try to start an XP project with 40 developers on day
      > one, I find it
      > difficult to envisage success.
      >
      >
      > > -----Original Message-----
      > > From: andre.claassen@... [mailto:andre.claassen@...]
      > > Sent: 26 February 2002 06:23
      > > To: extremeprogramming@yahoogroups.com
      > > Subject: Re: [XP] Another tools question - acceptance test
      > frameworks
      > > this time
      > >
      > >
      > > Hi,
      > >
      > >
      > > > Everyone seems to end up rolling their own. I would think
      > > xUnit would
      > > > be a good engine, but where it's 95% of the infrastructure
      > > needed for
      > > > programmer/unit/mobility tests, it's 5% of the
      > infrastructure needed
      > > > for acceptance/customer tests.
      > > >
      > > > Kent
      > >
      > > We currently develope a classic client/server Application for
      > > the public
      > > sector in VB / Visualc C++. (I hate VB :-)
      > >
      > > For acceptance tests, we have first played with the
      > > WinRunner-Software from
      > > Mecury. But this tool needs too much programming experience,
      > > to be useful
      > > for our customers.
      > >
      > > Our second try was a self written very simple script
      > > language, which is
      > > internally based on events.
      > > This script language can handle both gui stuff and
      > application logic.
      > >
      > > Example:
      > >
      > > MenuOpen "New"
      > > DialogClick "Generate Number"
      > > DialogField Name, "Test"
      > >
      > > Test Num of Persons, 10
      > > Test xxx
      > > ยด
      > > bye, Andre
      > >
      > >
      > >
      > >
      > > To Post a message, send it to: extremeprogramming@...
      > >
      > > To Unsubscribe, send a blank message to:
      > > extremeprogramming-unsubscribe@...
      > >
      > > ad-free courtesy of objectmentor.com
      > >
      > > Your use of Yahoo! Groups is subject to
      > http://docs.yahoo.com/info/terms/
      >
      >
      >
      > **************************************************************
      > ************************************
      > The views expressed in this E-mail are those of the author
      > and not necessarily those of Knowledge Management Software.
      > If you are not the intended recipient or the person
      > responsible for delivering to the intended recipient, please
      > be advised that you have received this E-mail in error and
      > that any use is strictly prohibited.
      >
      > If you have received this E-mail in error, please notify us
      > by forwarding this E-mail to the following address:
      >
      > mailadmin@...
      > **************************************************************
      > ************************************
      >
      >
      > To Post a message, send it to: extremeprogramming@...
      >
      > To Unsubscribe, send a blank message to:
      > extremeprogramming-unsubscribe@...
      >
      > ad-free courtesy of objectmentor.com
      >
      > Your use of Yahoo! Groups is subject to
      http://docs.yahoo.com/info/terms/



      **************************************************************************************************
      The views expressed in this E-mail are those of the author and not necessarily those of Knowledge Management Software.
      If you are not the intended recipient or the person responsible for delivering to the intended recipient, please be advised that you have received this E-mail in error and that any use is strictly prohibited.

      If you have received this E-mail in error, please notify us by forwarding this E-mail to the following address:

      mailadmin@...
      **************************************************************************************************
    Your message has been successfully submitted and would be delivered to recipients shortly.