black box testing - This test is not based on any knowledge of internal design or coding. These tests are based on the requirements and functionality.
white box testing - This is based on knowledge of the internal logic of the application code. The tests are based on a coverage of code statements, branches, paths, conditions.
Unit testing - the scale more 'micro' test; to test particular functions or code modules. This is typically done by the programmer and not by testers, as it requires the detailed knowledge of the internal program, and code. Not always easily done unless the application is well-designed architecture with tight code; It may require the development of test driver modules or harnesses tests.
Incremental integration testing - continuous testing of an application when you add new features; It requires that the various aspects of the functionality of an application to be independent enough to work separately before all parts of the program have been completed, or testers to be developed according to the needs; done by programmers or by testers.
Integration testing - testing of combined parts of an application to determine if it works properly together. The "actors" can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client / server and distributed systems.
Functional test - this test is oriented to the functional requirements of an application; This type of test should be done by testers. This does not mean that programmers should not check that their code works before releasing
Testing System - This is based on overall requirements specifications (which of course applies to any testing.); It covers all combined parts of a system.
end-to-end testing - this is similar to system testing; It involves the testing of a complete application environment in a situation that mimic real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications or systems.
sanity testing or smoke testing - usually it comes to an initial test to determine if a new software version is performing well enough to accept for a major testing effort. For example, if the new software freezes systems every 5 minutes, making the systems to be scanned or corrupted database, the software may not be in a normal condition to warrant further testing in its current state.
Regression testing - this is the re-testing after bug fixes or modifications of the software. It is difficult to determine how much you need to re-test, especially at the end of the development cycle. automated testing tools are very useful for this type of test.
Acceptance Testing - this can be said as a final test and this was done on the basis of specific end-user or customer, or on the basis of use by users / customers over a certain period of limited time.
load test - this is nothing more than the application testing in the presence of heavy loads, how to test a website in a wide range of loads to determine at what point the system's response time degrades or fails.
The stress test - the term often used interchangeably with 'load' and testing 'performance'. Also used to describe such tests as a functional test of the system, though in the case of particularly heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.
performance testing - the term often used interchangeably with 'stress' testing and 'load'. Ideally 'performance' testing is defined in the documentation or QA requirements or test plans.
usability test - This test is made to 'ease'. Clearly this is personal, and will depend on the end user or targeted customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not suitable as usability testers.
Compatibility testing - testing how well the software performs in a particular hardware / software / operating system / network / etc environment.
user acceptance testing - to determine if the software is satisfactory to an end user or customer.
Comparison tests - comparing software weaknesses and strengths to other competing products.
Alpha testing - if an application development testing is being completed; minor design changes can still be made as a result of such tests. This is typically done by users or other, but not for programmers or testers.
Beta testing - testing when the development and testing are essentially completed and final bugs and problems need to be found before the final release. This is typically done by users or others, not by programmers or testers.
Mutation testing - a method of determining a test data set or test cases it is useful or not, intentionally introducing various changes to the code ( 'bugs') and repeat the test with the original data test / cases are detected to determine whether the 'bugs'.
0 Komentar