Across
- 3. This testing is executing a previously failed test against new software to check if the problem is resolved
- 7. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load.
- 8. Testing which is carried out without using any automated tool or any script.
- 9. In this testing the software to check if it can inter-operate with other software component, software’s or systems.
- 10. This testing is a type of systems testing designed to determine whether individuals with disabilities will be able to use the system in question, which could be software, hardware, or some other type of system
- 12. Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
- 14. Testing the application as a whole for the modification in any module or functionality.
- 15. Testing typically done by end-users or others. Final testing before releasing application for commercial purpose.
Down
- 1. Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.
- 2. This is a type of testing which is an attempt to evaluate the security of an IT infrastructure by safely trying to exploit vulnerabilities
- 4. Testing done for the software in order to verify that the software is stable enough for further testing.
- 5. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing.
- 6. Testing to determine if a new software version is performing well enough to accept it for a major testing effort.
- 11. This testing is an approach to software testing that is concisely described as simultaneous learning, test design and test execution.
- 13. Can system be penetrated by any hacking way. Testing how well the system protects against unauthorized internal or external access.