
	Where results make sense

Topic: Regression testing

Related Topics

Software testing

System testing

Stress testing

Integration testing

Installation testing

Load testing

Performance testing

User acceptance testing

Conformance testing

Usability testing

Software engineering

Stability testing

	Regression testing - Wikipedia, the free encyclopedia
		Regression testing is any type of software testing which seeks to uncover regression bugs.
		Regression testing is an integral part of the extreme programming software development methodology.
		Regression testing can be used not only for testing the correctness of a program, but it is also often used to track the quality of its output.
	en.wikipedia.org /wiki/Regression_test (495 words)

	Information Security Glossary - Regression Testing
		Regression Testing is a process which tests a system once again to ensure that it still functions as expected / as per specification.
		N.B. Regression Testing must also test the revised software by simulating its operational environment to ensure that all systems and interfaces still operate as expected.
		Regression Testing should be conducted as per any system testing as proceed according to a Test Plan.
	www.yourwindow.to /information-security/gl_regressiontesting.htm (215 words)

	Examples of Regression Testing
		Regression testing is a style of testing that focuses on retesting after changes are made.
		In addition, proponents of traditional regression testing argue that retesting is a measurement or control process, a means of assuring that the program is as stable as it was previously.
		The essence of regression testing is exposure of problems that shouldn't be there, either because they were exterminated before or they weren't in the product the last time(s) it was tested.
	www.testingeducation.org /k04/RegressionExamples.htm (574 words)

	xRegress for regression testing (Site not responding. Last check: 2007-10-08)
		The purpose of regression testing is to ensure that changes made to software, such as adding new features or modifying existing features, do not adversely affect features of the software that should not change.
		Regression testing must be conducted to confirm that recent program changes have not adversely affected existing features and new tests must be created to test new features.
		In practice, depending on the available resources, a trade-off between what we can do in regression testing and what we can afford to do is applied to determine which test, among those necessary, should be re-executed first, and which one has lower priority or is to be omitted from re-execution.
	xsuds.argreenhouse.com /html-man/xregress.html (2778 words)

	Software Regression Testing.
		The purpose of regression testing is to exercise all code paths fully and to confirm that the software under test continues to function as expected.
		Tests must be designed carefully so as to minimise unnecessary maintenance work on test scripts whenever software changes are made, yet retain their effectiveness at detecting differences.
		Regression tests around software integration points in particular must be constructed to ensure impact on external systems is detected as early as possible.
	www.visibleprogress.com /software_regression_testing.htm (1156 words)

	Regression Testing with Tessy (Site not responding. Last check: 2007-10-08)
		Regression tests are thus re-runs of successfully completed test cases.
		Regression testing often is necessary for software to be revised in terms of code size, performance, maintenance and reusability, while at the same time guaranteeing that existing functionality remains unchanged.
		The pre-requisite for ensuring test cases are compatible with the latest version of software is that test data, including data for modified interfaces, is reusable in the most efficient and extensive means possible.
	www.hitex.com /con_regression_testing_with_tessy.html (296 words)

	A Roadmap for Regression Testing of Relational Databases
		Testing late in the lifecycle is better than nothing, but as Barry Boehm noted in the early 80s it's incredibly expensive to fix any defects you find at that point.
		As you have seen, database testing is something that is done continuously by the people on development teams, it isn't something that is done by another group (except of course for system testing efforts).
		To ensure a clean database, a common strategy is that at the beginning of each test run you drop the database, then rebuild it from scratch taking into account all database refactorings and transformations to that point, then reload the test data, and then run your tests.
	www.agiledata.org /essays/databaseTesting.html (3058 words)

	Regression Testing - AEP Practices
		Regression testing is the process of running all existing test cases and verifying that all test cases pass.
		The purpose of regression testing is to detect unexpected faults—especially those faults that occur because a developer did not fully understand the internal code correlations when he or she modified or extended code that previously functioned correctly.
		Regression testing is the only reliable way to ensure that modifications did not introduce new errors into code or to check whether modifications successfully eliminated existing errors.
	www.parasoft.com /jsp/aep/aep_practices.jsp?practice=RegTesting&itemId=193 (238 words)

	Worksoft’s Regression Testing Solution: Progression Testing (Site not responding. Last check: 2007-10-08)
		Adding 10% of the existing code base in a new release requires 110% test coverage to assure both old and new functionality are working, yet the time and resources usually applied to testing all of this functionality are at best flat release over release, and more likely declining.
		Regression testing is typically performed by quality assurance, while new capabilities must be verified and accepted by the business analysts and application experts through functional and acceptance testing.
		Regression testing may be automated if the QA has the technical skills available; traditional recording and scripting automation tools require coding skills and only work with existing features.
	www.worksoft.com /ContentDisplay/G11/G11L54.asp (317 words)

	AdventNet QEngine - Regression Testing
		Transfer of Build to test machine, execution of tests and transfer of reports to a central report server are all carried out in an interventionless mode.
		It allows viewing of details regarding the Test Machines in the regression test environment, selecting and sorting of test cases based on severity, and Case ID for test execution, and viewing quality-status reports of the Application Under Test.
		Test Progress Report gives a comparison between the test case count (in terms of passed, failed, incomplete, and error) taken up for testing and the actual number of test cases available in the Master.
	www.adventnet.com /products/qengine/regression-testing.html (229 words)

	Regression testing
		Regression testing means “repeating a test already run successfully, and comparing the new results with the earlier valid results”.
		Regression testing is based on the idea of reusing a test and acceptance standard, rather than forgetting about them once the test is successful.
		Regression tests begin as soon as there is anything to test at all.
	www.automatedqa.com /Products/testcomplete/tc_regression_testing.asp (415 words)

	Technical Papers - Regression Testing
		Testing to make sure the software hasn't taken a step backwards, or "regressed", is called "regression testing".
		Anything that goes wrong with the old tests can be traced to something done between the last time the regression test was run, and the time the latest one has run.
		The last thing we need is automated test software that forces us to figure out why things didn't work out as regards running the tests, rather than as regards their results.
	www.automatedqa.com /techpapers/regression.asp (1376 words)

	Pattern your way to automated regression testing
		Frequent testing is one of the extreme programming fundamentals, a set of practices growing in popularity because it provides a sound approach to dealing with the inevitable complexity and change of today's programming projects.
		In the past, a major obstacle to adequate unit testing was the inherent startup costs to design and implement an acceptable unit-testing framework.
		Without a framework, unit tests were haphazardly implemented, and very difficult to aggregate into test suites that ran with the click of a button.
	www.javaworld.com /javaworld/jw-09-2001/jw-0921-test.html (1203 words)

	Functional Testing \| Regressing Testing \| Testing Tools - ReadyTestGo
		Regression testing is a time consuming and tedious exercise that involves testing after making a functional improvement or repair to the system.
		Regression tests are similar in scope to functional tests and aim for consistent, repeatable validation of each new release of an application.
		Our regression testing services ensure that the reported product defects are corrected for each new release and that no new quality problems were introduced in the maintenance process.
	www.readytestgo.com /regression-testing.htm (181 words)

	Regression Testing Process
		The build details, the zip name, the OS for which this build is made, the date of creation of build, and the name of test group to which this new build has to be sent for testing are also sent to the regression manager.
		The regression server receives the build from the regression manager if the build zip name, build date, and test group of the newly arrived build matches the test environment it is mastering.
		Test results in the test machine are sent to the report server on completion of each test run(QEngine executes unassociated test cases together.
	www.adventnet.com /products/qengine/help/nightly_builds/nightly_build_process.html (398 words)

	QACenter Regression Testing
		Test reliability is increased by enabling the test script to make decisions about the flow of the automation process.
		Issues and defects identified during testing or development can be immediately associated with the requirement that is affected, allowing team members to assess the impact and project managers to analyze the status of the project.
		Testing requirements generated in Reconcile can be used to automatically generate or update an automated test suite in Compuware's test management tool.
	www.operativesoft.com /html/qacentere.htm (4252 words)

	Regression testing your Pocket PC app, a new form of torture
		We have been testing this app manually for the last 3 months so I was pretty happy to find that there is a solution to this tedium in the form of Spb's Pocket PC Test Suite.
		Regression testing is the selective retesting of a software system that has been modified to ensure that all bugs have been fixed and that no other previously-working functions now fail as a result of new 'fixes'.
		There are several testing scenarios that can be used only in conjunction with automatic testing, for example, performing a large number of iterations of similar actions or tracking memory leaks between certain testing cycles.
	www.devbuzz.com /content/pocket_pc_testing_automated_pg1.asp (785 words)

	BBSTRegressionTesting
		Regression testing involves reuse of tests to manage risks of change.
		We might test for effectiveness of a bug fix, impact on other bug fixes, or general side effects of change on the supposedly-unchanged parts of the program.
		We might do regression test by repeating the exact same test as before, or we might reuse the prior test idea, using different data and different secondary conditions as varying items across different uses of the test.
	www.testingeducation.org /BBST/BBSTRegressionTesting.html (258 words)

	Data Flow Type Regression Testing (Site not responding. Last check: 2007-10-08)
		With testing, the only way to guarantee a program's correctness is to verify it on all possible inputs, which is clearly impossible.
		In data flow testing, a variable assignment in a program is tested by generating test that execute subpath from assignment (definition) to points where the variable's value is used (use).
		Test data adequacy criteria are used to select particular def-use associations to test.
	www.umiacs.umd.edu /~hismail/Omega/node12.html (429 words)

	Infogain - Infogain's Automated Regression Testing Solution (Info ART) (Site not responding. Last check: 2007-10-08)
		The testing cycle is long as the automated regression test suite is either not available or was not maintained properly and therefore cannot be used
		Testing of the product on tier II and tier III platforms involves huge effort and therefore, the product on these platforms is released 3 to 6 months after the tier I platforms.
		Test suite is useable any time within the development life cycle as it is maintained on a continuous basis
	www.infogain.com /automated-reg-testing.jsp (445 words)

	Regression Testing Definition
		Regression testing is a normal part of the program development process and, in larger companies, is done by code testing specialists.
		REGRESSION TESTING DEFINITION (continued): … Regression testing is the process of testing changes to computer programs to make sure that the older programming still works with the new changes.
		Test department coders develop code test scenarios and exercises that will test new units of code after they have been written.
	www.bitpipe.com /tlist/Regression-Testing.html (393 words)

	Performing Regression Testing
		Jtest performs regression testing, along with all other appropriate types of testing, each time that you test a class or set of classes that has already been tested at least once.
		The Class Testing UI is used to test a single class; the Project Testing UI is used to test a set of files.
		Regression errors found will be reported in the Specification and Regression Errors branch of the Errors Found Panel (if you tested a single class) or the Results Panel (if you tested a project).
	www.cs.indiana.edu /csg/links/parasoft/jtest/test_reb.htm (324 words)

	Regression Testing Course - Overview Of The Course
		Testing changes to an existing system is more difficult than testing new code because of the danger that a change will inadvertently break something else.
		This class presents the special techniques needed for testing changes to the system, whether those changes are enhancements or bug fixes.
		Symptoms include large test sets of unknown content, lots of redundant tests, and bugs that slip through even though we supposedly used regression testing to eliminate the side effects of changes.
	www.testingcenter.com /oviewce.html (260 words)

	Binary Regression Testing
		The purpose of the Binary Regression Test (BRT) project is to be able to execute regression test suites focused on specific proprietary binaries.
		The major goal is to shorten the passage of time in the development cycle between when a code change happens and when it is noticed to have an adverse effect on the execution of the binary.
		Specifically, this means we will design a system that should make it easy to run regression tests on a pre-defined linux system which will be upgraded in the time frame of the open source projects and compile the results of those tests.
	developer.osdl.org /dev/brt (1115 words)

	Chapter 16. Regression Testing
		In Chapter 13, Unit Testing, you learned about the philosophy of unit testing.
		It takes unit tests that you've written for individual modules, collects them all into one big test suite, and runs them all at once.
		Each such script should be a test suite that tests a module through PyUnit.
	diveintopython.org /regression_testing/index.html (478 words)

	Functionality Testing and Regression Testing of Software application and Products (Site not responding. Last check: 2007-10-08)
		Developing accurate, clear and concise test cases is critical to the success of functional and regression testing.
		We have performed functional and regression testing for a wide array of applications including those in the Financial Services, Healthcare, and Technology sectors.
		Each testing team established is 100% dedicated to their project.
	www.applabs.com /functional_testing.htm (437 words)

	Mosaic Test Automation Services; Regression Testing
		In order to efficiently regression test in these environments, testers need to automate the testing of high volume transactions, data-driven transactions, and n-tier interfaces.
		Mosaic, Inc. can help automate these tests so that fewer resources and a lot less time are needed to execute the tests.
		Assist with the development of a test automation strategy within an organization or for a specific project including determination of appropriate applications for automation, development of an automation plan, and development and documentation of an automation process.
	www.mosaicinc.com /mosaicinc/test_automation.htm (232 words)

	Overview of Solaris Patch System Testing and Performance Regression Testing
		The System Test and Performance Regression Test cycle occurs in parallel to the Verification of bug fixes included in the patches.
		In-house developed test suite to test that the source browsing utilities (sbe) implemented by commands such as sbcat, sbquery, and sbdump continue to work on a patched Solaris system.
		A node failover is triggered during the test suite execution to check that SunCluster failover is unaffected by the Solaris patches.
	sunsolve.sun.com /pub-cgi/show.pl?target=patches/sys-and-perf-test (2138 words)

Try your search on: Qwika (all wikis)