Regression On Large Systems – How To Test

5 pts.
Tags:
Agile
Agile adoption
Agile testing
Automation Test
Regression
So, I ahve been working at a company that has struggled with transitionaing into an Agile. The product we work on invovles accounting at a commercial level...very large in scope. Quality has been slipping and the organization has no regression testing in place. We have currently been given the task to bring up some sort of regression suite. Is this the right approach. How do you effectively ensure functionality is not breaking without creating such a huge regression suite that cannot be run. How much do you automate and what do you target. How do teams become dynamic in this respect. It seems impossible.

Software/Hardware used:
Silverlight, RIA Services, Entity Farmework, .NET, Agile

Answer Wiki

Thanks. We'll let you know when a new response is added.

Regression testing is paramount no matter what size the system is! Start by committing resources and time towards establishing a regression testing team/strategy and execute accordingly. There is no excuse for not regression testing and quality issues will invariably occur if overlooked. A little focus will go a long way so start regression testing immediately.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Justin Rohrman
    This is a very very big question, but a reasonable question might be 'how much regression testing do you need for this release'. Automated test suites take time to develop and maintain so that won't immediately help you, though you and your team may want to begin thinking about where you can implement some sort of automation. I am a fan of starting at the API.

    Quality slipping isn't a testing problem, it is a project and development problem. Think about ways to increase code quality before the product gets to test. Developing in smaller increments and adding checks like unit tests can be helpful.
    730 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following