The difference between functional testing and regression testing

The difference between functional testing and regression testing

Are UAT (functional testing) and regression testing the same?

    Requires Free Membership to View

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Regression testing and UAT and functional testing are all different, in fact.

Regression testing is the act of retesting a product around an area where a bug was fixed. If a data access component is changed, for instance, to improve security, the code directly affected by that change will be regression tested. A good team will also test related code such as UI-based functions which leverage the methods and/or class impacted by the fix.

UAT, or user acceptance testing, is a waterfall test concept. Software solutions are developed, tested internally and then delivered to the customer/user for UAT. In this test activity, end-to-end scenarios are the focus. Generally testers are the business customers of an IT project, and very little negative testing takes place.

Functional testing is an overridden term most frequently used to refer to the testing of software features (functional points) individually. Emphasis is placed on functionality within the unit, and very little time is spent testing how that functional unit integrates with other functional units.

This was first published in April 2009