Comments:

Flat Nested Threaded Embedded

Oldest First Newest First

Here is the categories of Testing By eMSFTAdmin on Thursday, March 22, 2007 (UMST)

Here's an alphabetical list of testing methodologies that I haven't seen yet: Accessibility Testing: Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.). Compatibility Testing: Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware. Concurrency Testing: Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores. Conformance Testing: The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard. Conversion Testing: Testing of programs or procedures used to convert data from existing systems for use in replacement systems. Dependency Testing: Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality. Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution. Integration Testing: Testing of combined parts of an application to determine if they function together correctly. This type of testing is especially relevant to client/server and distributed systems. Recovery Testing: Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions. Regression Testing: Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made. Scalability Testing: Performance testing focused on ensuring the application under test gracefully handles increases in work load. Usability Testing: Testing the ease with which users can learn and use a product. Volume Testing: Testing which confirms that any values that may become large over time (such as accumulated counts, logs, and data files), can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner Reply to this Comment