IT is the process of stepping through all known bugs to verify that they have either been fixed or remain fixed from the last time they were regression tested. This means that all known and reported bugs should be put into some form of test error database or file.
When a new build is delivered from an engineering/development division to a testing division this "suite" of regression tests is generally run. More practically, regression testing also refers to any new features that were added to a given build since the last time testing was done to determine if those new features have caused any other problems with previous features.
IT is the process of checking out how the product and any system it might work with (such as a Web server or a network) handles its processing tasks under increasing demands. This is mainly a concern for client/server and Web-based applications. (By contrast, desktop applications do not necessarily have to do this form of testing to the same extreme.) As just one example, a Web-based application that uses a search engine may have to be tested for the situation where five thousand users are performing different types of searches.
IT is the process whereby a given piece of software is checked for various compatibility issues, such as compatibility with prior versions, compatibility with existing software, and compatibility with different operating platforms. In the Web-based application world, compatibility often takes the form of checking for how well the Web-application works in different Web browsers as well as with different Web technologies.
IT is the process of testing a given piece of functionality in numerous different ways via permutations of the basic objects that make up the functionality or testing a given set of of elements that can be used in relation to the functionality.
from an automated perspective, is most applicable to the Web where the markup used to create Web pages is checked to determine if appropriate tag elements are used, if attributes for those tag elements are used, and if features that are used in the markup allow for certain usability or accessibility concerns. This is mainly used for a form of markup validation. (It should be noted that usability and accessibility are wide-scope issues and, as such, automation is only viable for a limited subset of that overall area of concern.)
refers to being able to test products that have a great deal of cross-referencing in the form of links or hypertext as in the case
of Web pages and help files (such as WinHelp or HTMLHelp). An automated tool can easily cycle through thousands of links in much less time then it would take a human tester.
Recovery testing is a system test that focuses the software to fall in a variety of ways and verifies that recovery is properly performed. If recovery is automatic, reinitialization, checkpointing mechanisms, data recovery and restart are evaluated for correctness. If recovery requires human intervention, the mean-time-to-repair (MTTR) is evaluated to determine whether it is within acceptable limits.
Security testing attempts to verify that protection mechanisms built into a system will, in fact, protect it from improper penetration. During Security testing, password cracking, unauthorized entry into the software, network security are all taken into consideration.
SOFTWARE QUALITY ASSURANCE AND CONTROL
SOFTWARE QUALITY AND COST ASPECT
STABLE PROCESS OF SOFTWARE TESTING
STABLE PROCESS OF SOFTWARE TESTING PART TWO
DEFECTS IN SOFTWARE TESTING
REDUCTION OF DEFECTS IN SOFTWARE TESTING
SOFTWARE TESTING AND EFFECTING FACTORS
SCOPE OF SOFTWARE TESTING
TESTING LIFE CYCLE PART ONE
TESTING LIFE CYCLE PART TWO
TESTING LIFE CYCLE PART THREE
SOFTWARE TESTING AND CONSTRAINTS WITH IN IT
TESTING CONSTRAINTS PART TWO
LIFE CYCLE TESTING
Independent Software Testing
Testing verification and validation
Functional and structural testing
Static and dynamic testing
V model testing
Eleven steps of V model testing
Execution testing technique
Recovery Testing technique
Operation testing technique
Compliance software testing technique
Security testing technique