I really appreciate your input Lisa.
Thanks
Avanthi polavarapu

On Feb 13, 2012, at 5:22 PM, Lisa Crispin <lisa.crispin@...> wrote:

 

+1 on Andrew's response.

When my current team first implemented agile, we also didn't have any automated regression tests. We released every two weeks. We spent the last two days of each release having everyone on the team divide up and execute the scripted manual regression tests. This was great motivation for every developer to think about good ways to solve test automation problems.

Test automation is simply a part of software development. It isn't a separate activity. The same people who write production code also must write test code. The testers specify what test cases to automate, the inputs and expected results. There are many ways to accomplish this.

I highly recommend Gojko Adzic's book Specification by Example, http://specificationbyexample.com, as a starting place for your entire development team (or all your teams if you have more than one) to start learning how to achieve a sustainable pace along with high quality code by integrating testing into coding.

Of course, there are other testing activities where testers' specialized skills will contribute value, such as exploratory testing. But you won't have time for that if you force testers to try to solve regression testing problems by themselves.

You probably have lots of problems at this point. It takes a long time to find ways to improve your development. Get everyone on your team together for a retrospective, identify your biggest problem, think of some small experiment that will help make the problem less bad, and try it. Then see how that worked, and continue on.
-- Lisa

On Mon, Feb 13, 2012 at 1:34 PM, Avanthi <avanthi_48307@...> wrote:

 

Hey Lisa,

Unfortunately we do not have any automation tests.I recorded/scripted selenium in the beginning but code changes were too frequent that kept breaking my scripts.The work was done in atleast 5 branches.
Also I am one person onsite and we have one person Offshore helping me. Crazy approach that they have followed in developing the code in various branches and then merging it .

Thanks
Avanthi

--- In agile-testing@yahoogroups.com, Lisa Crispin <lisa.crispin@...> wrote:
>
> Hi Avanthi,
> Do you not have any automated regression tests that ensure that the code
> checked in each sprint continues to work properly?
>
> This is not a problem for two testers to solve. It's a problem for your
> whole development team to solve. And they should all be helping with the
> testing effort. Get them all together and think of some experiments to try.
> -- Lisa
>

> On Mon, Feb 13, 2012 at 1:25 PM, Avanthi <avanthi_48307@...> wrote:
>
> > **

> >
> >
> > Hi ,
> >
> > We are following Agile Methodology in our company .We atleast had 6
> > sprints (with atleast 20 stories per sprint) done by the time we are going
> > to launch the final release for product .
> >
> > Now the questions comes is that our leads are expecting me to do
> > regression testing for all the works done in various sprints on various
> > branches as all of them are getting merged to Master branch.
> >
> > I am given a month time to do all this and we are two people .Any thoughts
> > on how I should be planning my regression testing for this big launch .
> >
> > Appreciate any feedback .
> > Thanks
> > AP
> >
> >
> >
>
>
>

> --
> Lisa Crispin
> Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers
> and Agile Teams_ (Addison-Wesley 2009)
> Contributor to _Beautiful Testing_ (O'Reilly 2009)
> http://lisacrispin.com
> @lisacrispin on Twitter
> http://entaggle.com/lisacrispin
>

--
Lisa Crispin
Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers and Agile Teams_ (Addison-Wesley 2009)
Contributor to _Beautiful Testing_ (O'Reilly 2009)
http://lisacrispin.com
@lisacrispin on Twitter
http://entaggle.com/lisacrispin

=