Civil Rights
Movements, leaders, victories and the continuing fight for equality.
q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
Explore the people, places, events, achievements, struggles and stories that shaped our journey.
Movements, leaders, victories and the continuing fight for equality.
Innovation, patents, science, technology and world-changing contributions.
Pioneers, champions, Negro Leagues, records, activism and excellence.
Meet the people whose lives, choices and achievements shaped the journey.
Black towns, communities, institutions and places where history happened.
Moments that changed communities, movements, institutions and the nation.
Katherine Johnson’s mathematical calculations helped guide some of America’s most important early space missions while she confronted the racial and gender barriers faced by Black women in twentieth-century America.
MORE →Reflects the personal views, recollections, and perspective of the author, Mike Davis.
This is a personal recollection on the Move fire on May 13, 1985
| Part of a series on |
| Software development |
|---|
Regression testing (rarely, non-regression testing[1]) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change.[2] If not, that would be called a regression.
Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components (hardware).[3] As regression test suites tend to grow with each found defect, test automation is frequently involved. Sometimes a change impact analysis is performed to determine an appropriate subset of tests (non-regression analysis[4]).
As software is updated or changed, or reused on a modified target, emergence of new faults and/or re-emergence of old faults is quite common.
Sometimes re-emergence occurs because a fix gets lost through poor revision control practices (or simple human error in revision control). Often, a fix for a problem will be "fragile" in that it fixes the problem in the narrow case where it was first observed but not in more general cases which may arise over the lifetime of the software. Frequently, a fix for a problem in one area inadvertently causes a software bug in another area.
It may happen that when a feature is redesigned some of the same mistakes that were made in the original implementation of the feature also occur in the redesign. In most software development situations, it is considered good coding practice, when a bug is located and fixed, to record a test that exposes the bug and re-run that test regularly after subsequent changes to the program.[5]
Although this may be done through manual testing procedures using programming techniques, it is often done using automated testing tools.[6] Such a test suite contains software tools that allow the testing environment to execute all the regression test cases automatically; many projects have automated continuous integration systems to re-run all regression tests at specified intervals and report any failures (which could imply a regression or an out-of-date test).[7]
Common strategies are to run such a system after every successful compile (for small projects), every night, or once a week. Those strategies can be automated by an external tool.[8]
Regression testing is an integral part of the extreme programming software development method.[9] In this method, design documents are replaced by extensive, repeatable, and automated testing of the entire software package throughout each stage of the software development process. Regression testing is done after functional testing has concluded, to verify that the other functionalities are working.
In the corporate world, regression testing has traditionally been performed by a software quality assurance team after the development team has completed work. However, defects found at this stage are the most costly to fix. This problem is being addressed by the rise of unit testing. Although developers have always written test cases as part of the development cycle, these test cases have generally been either functional tests or unit tests that verify only intended outcomes. Developer testing compels a developer to focus on unit testing and to include both positive and negative test cases.[10]
The various regression testing techniques are:
This technique checks all the test cases on the current program to check its integrity. Though it is expensive as it needs to re-run all the test cases, it ensures that there are no errors because of the modified code.[11]
Unlike Retest all, this technique runs a part of the test suite (owing to the cost of retest all) if the cost of selecting the part of the test suite is less than the Retest all technique.[11]
Prioritize the test cases so as to increase a test suite's rate of fault detection. Test case prioritization techniques schedule test cases so that the test cases that are higher in priority are executed before the test cases that have a lower priority.[11]
This technique is a hybrid of regression test selection and test case prioritization.[11]
Regression testing is performed when changes are made to the existing functionality of the software or if there is a bug fix in the software. Regression testing can be achieved through multiple approaches; if a test all approach is followed, it provides certainty that the changes made to the software have not affected the existing functionalities, which are unaltered.[12]
In agile software development—where the software development life cycles are very short, resources are scarce, and changes to the software are very frequent—regression testing might introduce a lot of unnecessary overhead.[12]
In a software development environment which tends to use black box components from a third party, performing regression testing can be tricky, as any change in the third-party component may interfere with the rest of the system (and performing regression testing on a third-party component is difficult, because it is an unknown entity).[12]
Regression testing can be used not only for testing the correctness of a program but often also for tracking the quality of its output.[13] For instance, in the design of a compiler, regression testing could track the code size and the time it takes to compile and execute the test suite cases.
Also as a consequence of the introduction of new bugs, program maintenance requires far more system testing per statement written than any other programming. Theoretically, after each fix, one must run the entire batch of test cases previously run against the system to ensure that it has not been damaged in an obscure way. In practice, such regression testing must indeed approximate this theoretical idea, and it is very costly.
— Fred Brooks, The Mythical Man Month, p. 122
Regression tests can be done at any level, from unit through to system integration. Functional tests exercise the complete program with various inputs. These tests are often automated due to the need for repetition, and may be done by test tools that are not part of the compiler suite. Non-functional tests assess aspects such as performance, security, or reliability. Conducting non-functional regression tests presents additional challenges. For example, detecting changes in performance is often statistically complex,[14] while security issues typically arise from vulnerabilities in the software ecosystem rather than from individual code changes.[15]
Testing activities that focus on regression problems are called (non) regression testing. Usually "non" is omitted
{{cite conference}}: Cite uses deprecated parameter |citeseerx= (help)
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
Regression testing (rarely, non-regression testing) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change. If not, that would be called a regression. Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components (hardware). As regression test suites tend to grow with each found defect, test automation is frequently involved. Sometimes a change impact analysis is performed to determine an appropriate subset of tests (non-regression analysis).
In software development, dynamic testing (or dynamic analysis) is examining the runtime response from a software system to particular input (test case). Tests can be run manually or via automation. Unit testing, integration testing, system testing, regression testing and acceptance testing are forms of dynamic testing. In contrast to static testing, the software must be runnable.
A software regression is a type of software bug where a feature that has worked before stops working correctly. This may happen after changes are applied to the software's source code, including the addition of new features and bug fixes. They may also be introduced by changes to the environment in which the software is running, such as system upgrades, system patching or even a change to daylight saving time. A software performance regression is a situation where the software still functions correctly, but performs more slowly or uses more memory or resources than before. Various types of software regressions have been identified in practice, including the following: Local – a change introduces a new bug in the changed module or component. Remote – a change in one part of the software breaks functionality in another module or component. Unmasked – a change unmasks an already existing bug that had no effect before the change. Regressions are often caused by encompassed bug fixes included in software patches. One approach to avoiding this kind of problem is regression testing. A properly designed test plan using automated testing and well-written test cases aims at preventing regressions before software or software updates are released.
Cypress is a frontend test automation tool (framework) for regression testing of web applications including End-to-End (E2E), integration, and unit tests. Cypress runs on Windows, Linux, and macOS. The Cypress app is open-source software released under the MIT License, while Cypress Cloud is a commercial software as a service web application with free and paid plans. Cypress has been compared to Selenium.
Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.
MORE →Shirley Chisholm, elected in 1968.
