1) The approach/document used to make sure all the requirements are covered when writing test cases a) Test

Matrix b) Checklist c) Test bed d) Traceablity Matrix 2) Executing the same test case by giving the number of inputs on same build called as a) Regression Testing b) ReTesting c) Ad hoc Testing d) Sanity Testing 3) A Non-Functional Software testing done to check if the user interface is easy to use and understand a) Usability Testing b) Security Testing c) Unit testing d) Block Box Testing 4) Variance from product specifications is called? a) Report b) Requirement c) Defect 5) White box testing is not called as___________ a) Glass box testing b) Closed box testing c) OPen box testing d) Clear box testing 6) Retesting of a single program or component after a change has been made? a) Full Regression Testing b) Unit Regression c) Regional Regression d) Retesting 7) The testing which is done by going thro' the code is known as, a) Unit Testing b) Blackbox testing c) White box Testing d) Regression testing 8)This type of testing method attempts to find incorrect or missing functions, errors in data structures or external database access, interface errors, Performance errors and initialization and Termination errors. It is called as a) White Box Testing b) Grey Box Testing c) Black Box Testing d) Open Box Testing 9) Software testing which is done without planning and Documentation is known as a) adHoc Testing b) Unit Testing c) Regression testing d) Functional testing.

10) Acceptance testing is known as a) Beta Testing b) Greybox testing c) Test Automation d) White box testing 11) Retesting the entire application after a change has been made called as? a) Full Regression Testing b) Unit Regression c) Regional Regression d) Retesting 12) Boundary value analysis belongs to which testing method? a) Black Box testing b) White Box testing

13) The name of the testing which is done to make sure the existing features are not affected by new changes a) Recursive testing b) Whitebox testing c) Unit testing d) Regression testing 14) AdHoc testing is a part of a) Unit Testing b) Regression Tesing c) Exploratory Testing d) Performance Testing 15) ------------- means under what test environment(Hardware, software set up) the application will run smoothly a) Test Bed b) Checkpoint c) Code Walk through d) Checklist 16) Unit Testing will be done by a) Testers b) End Users c) Customer d) Developers 17) A Plan to overcome the risk called as a) Migration Plan b) Master plan c) Maintenance plan d) Mitigation Plan

http://qualitypoint.blogspot.in/2010/01/software-testing-quiz-questions-and.html#soft_test_ans

Types of Software Testing

This is a list of different types of software testing. Once you are at the point of alpha testing or beta testing your product or website, we highly recommend you use Pay4Bugs to get a crowd of software testers to find bugs in your product at the prices you choose!

BLACK BOX TESTING

Testers do not have access to, or knowledge of, the inner workings of the system being tested.Tests are based on requirements and functionality.

WHITE BOX/GLASS BOX TESTING

Testers have knowledge of the systems internal logic, and in this type of testing, the application logic is what is being tested. When defects are discovered, the tester must examine the code to see exactly where the defect occurred.

UNIT TESTING
Testing of individual software components or modules. Since a detailed, in-depth knowledge of the internal application logic is required, unit testing is normally performed by the developers who are working on the system. Unit testing may require the development of test driver modules or test harnesses.

INCREMENTAL INTEGRATION TESTING

Continuous testing of an application as new functionality or modules are added. This requires the modules to be independent enough to test separately. Incremental integration is done by programmers or by testers.

INTEGRATION TESTING
Testing of integrated modules to verify that they work together properly. Modules can include, but are not limited to, code modules, individual applications, and client and server applications on a network. This type of testing is especially relevant to client/server and distributed systems.

FUNCTIONAL TESTING
Functional testing focuses on the output, and whether it performs as the requirements and specs say it should perform. Functional testing is a type of black-box testing.

SYSTEM TESTING
The entire system is tested to make sure it performs as the requirements and specs say it should perform. System testing is a type of black-box type testing that is based on overall requirements and specifications, and, covers all combined parts of a system.

END-TO-END TESTING
Similar to system testing. End-to-end testing involves testing of a complete application environment in a situation that mimics real-world use. This includes using production components like databases, using network communications, or interacting with other hardware, applications, or systems.

SANITY TESTING
Sanity tests determine if a new software version is performing well enough to accept it for a major testing effort. These tests test the stability of an application. If the application crashes too often for initial use, the system is deemed to be too unstable for further testing.

REGRESSION TESTING
Regression testing ensures that fixes correcting newer defects do not re-introduce problems with older defects. Often, regression testing is automated because it is difficult to cover the entire system with manual tests.

ACCEPTANCE TESTING
This type of testing is performed by the customer to ensure that the system meets their specifications and requirements. Typically one of the last procedures before the user or customer accepts the application for production use.

LOAD TESTING
Load testing checks system behavior under heavy load (e.g. heavy network traffic or database load). Example: testing of a web site under a range of loads to determine at what point the systems response time degrades or fails.

STRESS TESTING
System is stressed beyond its specifications to check how and when it fails. Examples of components that are stress-tested are: mass-storage capacity, complex database queries, and database load.

PERFORMANCE TESTING
This term is often used interchangeably with stress and load testing. Performance tes ting checks whether system meets performance requirements, using different performance and load tools.

USABILITY TESTING
Usability testing checks for User-friendliness in other words, whether or not the application behaves the way the user expects it to behave. Application flow and UI are tested to determine whether a typical user will have any problems using the system, and whether or not the system is properly documented.

INSTALL/UNINSTALL TESTING
Full, partial, and upgrade install/uninstall processes are tested on different operating systems and under different hardware/software environments.

RECOVERY TESTING
Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

SECURITY TESTING
How secure is the system? Can the system be breached in any way? How well does the system protect against unauthorized internal or external access? Are the system and database safe from external attacks?

COMPATIBILITY TESTING
Compatibility testing measures how well software performs in different combinations of hardware/software/operating system/network environments.

COMPARISON TESTING
The system is compared against previous versions or other similar products, to determine its strengths and weaknesses.

ALPHA TESTING
Alpha testing is done in an in-house virtual user environment. Alpha testing is done at the end of development. Minor design changes may be made as a result of such testing.

BETA TESTING

Beta testing is typically done by end-users or others. This is the final stage before an application goes into commercial release. An application can be in a closed beta, tested only by people who have been invited to do the testing, or a public beta where anyone can obtain, tes t and provide feedback on the application.

PAY4BUGS
Pay4Bugs is a great tool that can be used in many different types of testing environments.