This article will helps you to aware all the software testing definitions which comes across the manual testing, the definitions are in very simple word to understand.
Software testing definitions:
testing an application under heavy loads(peak load), such as testing of a web site under a range of peak loads to determine at what point the system’s response time reduce or fails.
System functional testing while under heavy loads, certain actions or inputs, input of large numerical values, complex queries to a database system. Stress testing tries to break the system under test by overwhelming its resources (hardware or software) or by taking resources away from it (in which case it is sometimes called negative testing). The main purpose behind this madness is to make sure that the system fails and recovers gracefully — this quality is known as recoverability
term often used interchangeably with ‘stress’ and ‘load’ testing. Generally ‘performance’ testing is defined in business requirements documentation or Test Plans.
Performance testing and load testing can similar but their goals are different. Performance testing uses load testing techniques and tools for measurement and benchmarking purposes and uses various load levels and load testing operates at a predefined load level, usually the maximum load that the system can accept while still functioning properly. ensure that load testing does not aim to break the system by overwhelming it, but instead tries to keep the system constantly busy like a well-oiled machine.
- Install/Uninstall testing– test the full, partial, or upgrade install/uninstall processes.
- Recovery testing – test how system recovers from crashes, hardware failures
- Failover testing – Generally used interchangeably with ‘recovery testing’
- Security testing – test the how system protects against unauthorized internal or external access, willful damage.
- Compatibility testing – test how software performs in a particular hardware/software/operating system/network environment.
- Exploratory testing – Informal software test that is not based on test plans or test cases; testers may be learn the software as they test it.
- Ad-hoc testing – similar to exploratory testing, but the testers have significant understanding of the software before testing it.
- Context-driven testing – testing driven by an understanding of the environment and intended use of software.
- User acceptance testing – determining if software is satisfactory to an end-user or customer.
- Comparison testing – compare the software weaknesses and strengths to competing products.
- Alpha testing – test an application when development is near completion minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.
- Beta testing – testing when development and testing all phases are completed and final bugs and problems to be found before final release. Typically done by end-users.
Mutation testing – A method for determining the set of test data or test cases is useful, by deliberately introducing various code changes or bugs and retesting with the test data with test cases to determine if the bugs are detected.