Manual vs. Automated Testing Manual tests are those that require human intervention to perform a test procedure.

Automated tests can be designed to replicate any user/application activity in a high-speed and easily replicated environment. Not all tests should, or can be, automated. Certain processes that require human intervention, such as loading special paper into a printer, cannot be automated by a software tool. However, a good automated testing tool can easily incorporate necessary manual activities into an otherwise automated testing process. Automation is a Replacement of Manual Teseting : Test automation is expensive and it is an addition, not a replacement, to manual testing. It can be made cost-effective in the longer term though, especially in regression testing. One way to generate test cases automatically is model-based testing where a model of the system is used for test case generation, but research continues into a variety of methodologies for doing so.

In incremental model the real product is designed, implemented, integrated and tested as a series of incremental builds. while

Incremental development

Requirement Specification = Sum (R1, R2, R3,) R1 R2 R3 Design Design Design Coding Coding Coding Testing Testing Testing

The prototype becomes the first system.

This paradigm becomes useful when the customer defines general objectives of the software but does not identify detailed input, processing or output requirements. It may also be applied when the developer is unsure of the efficiency of an algorithm, or the way in which the human machine interaction. Various types of prototypes: Throwaway prototypes Evolutionary prototypes

In prototype model the prototype (not the real product) is designed, implemented, integrated and tested as a series of incremental builds

A simple difference between Black Box Testing and WhiteBox Testing Black Box testing is also known as behavioural or closed box testing. It is a software testing technique in which the internal workings of the item to be tested are not known to the tester or they are not taken into consideration. White Box Testing is also known as structural,open box, clear box or glass box testing. It is a software testing technique in which an explicit knowledge of the internal workings of the item to be tested are tested

ACCEPTANCE TESTING BLACK BOX TESTING

Testing to verify a product meets customer specified requirements. A customer usually does this type of testing on a product that is developed externally. Testing without knowledge of the internal workings of the item being tested. Tests are usually functional. Testing to ensure compatibility of an application or Web site with different browsers, OSs, and hardware platforms. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite.

COMPATIBILITY TESTING

CONFORMANCE TESTING

Verifying implementation conformance to industry standards. Producing tests for the behavior of an implementation to be sure it provides the portability, interoperability, and/or compatibility a standard defines. Validating an application or Web site conforms to its specifications and correctly performs all its required functions. This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product's user interface, APIs, database management, security, installation, networking, etcF testing can be performed on an automated or manual basis using black box or white box methodologies. Testing in which modules are combined and tested as a group. Modules are typically code modules, individual applications, client and server applications on a network, etc. Integration Testing follows unit testing and precedes system testing. Load testing is a generic term covering Performance Testing and Stress Testing. Performance testing can be applied to understand your application or web site's scalability, or to benchmark the performance in an environment of third party products such as servers and middleware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions. Similar in scope to a functional test, a regression test allows a consistent, repeatable validation of each new release of a product or Web site. Such testing ensures reported product defects have been corrected for each new release and that no new quality problems were introduced in the maintenance process. Though regression testing can be performed manually an automated test suite is often used to reduce the time and resources needed to perform the required testing. A quick-and-dirty test that the major functions of a piece of software work without bothering with finer details. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire. Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. A graceful degradation under load leading to non-catastrophic failure is the desired result. Often Stress Testing is performed using the same process as Performance Testing but employing a very high level of simulated load. Testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.

FUNCTIONAL TESTING

INTEGRATION TESTING

LOAD TESTING

PERFORMANCE TESTING

REGRESSION TESTING

SMOKE TESTING

STRESS TESTING

SYSTEM TESTING

UNIT TESTING

Functional and reliability testing in an Engineering environment. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration. Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing.

WHITE BOX TESTING

Grey box testing

Grey Box Testing (American spelling: gray box testing) involves having knowledge of internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level. The tester is not required to have a full access to the software's source code.[26][not in citation given] Manipulating input data and formatting output do not qualify as grey box, because the input and output are clearly outside of the "black-box" that we are calling the system under test. This distinction is particularly important when conducting integration testing between two modules of code written by two different developers, where only the interfaces are exposed for test. However, modifying a data repository does qualify as grey box, as the user would not normally be able to change the data outside of the system under test. Grey box testing may also include reverse engineering to determine, for instance, boundary values or error messages.