Innovative software testing solutions - tools and services for automated and manual testing of application software, Web sites, middleware, and system software. Are you going to start on a new project for testing? Don't forget to check this Testing Checklist in each and every step of your Project life cycle. List is mostly.

Complete website for Software Testing Folks. In Software Testing Class, you will get started with Software Testing Tutorials, Testing Articles & FAQs for free. Software Testing Fundamentals (STF) is a platform to gain (or refresh) basic knowledge in the field of Software Testing. If we are to

Software Testing and Quality Assurance Glossary. Last updated: Wednesday, 0. May- 2. 01. 3 0. 9: 4. PDTA (return to top of page)Acceptance Testing. Testing conducted to enable a user/customer to. Normally performed to.

Accessibility Testing. Verifying a product is accessible to the people having disabilities.

Ad Hoc Testing. A testing phase where the tester tries to 'break' the system by randomly. See. also Test Driven Development. Application Binary Interface (ABI). A specification defining requirements for portability of applications. Application Programming Interface (API). A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services. Automated Software Quality (ASQ).

The use of software tools, such as automated testing tools, to improve. Automated Testing. Testing employing software tools which execute tests without manual.

Can be applied in GUI, performance, API, etc. The process is repeated until the component at the top of the hierarchy is tested. Boundary Testing.

Test which focus on the boundary or limit conditions of the software being tested. C (return to top of page)CAST. Computer Aided Software Testing. Capture/Replay Tool.

A test tool that records test input as. The input cases stored can then.

Most commonly applied to. GUI test tools. CMM. The Capability Maturity Model for Software (CMM or SW- CMM) is a. Cause Effect Graph. A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

Code Complete. Phase of development where functionality is implemented in entirety; bug fixes. All functions found in the Functional Specifications. Code Coverage. An analysis method that determines which parts of the software have.

Code Inspection. A formal testing technique where the programmer reviews source code with. Code Walkthrough. A formal testing technique where source code is traced by a group. Coding. The generation of source code. Compatibility Testing. Testing whether software is compatible with other. Adobe Indesign Cs5 Free Trial Download on this page.

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. Usually applied to testing conformance to a formal. Context Driven Testing. The context- driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now. Conversion Testing. Testing of programs or procedures used to convert data from existing systems for use in replacement systems. Cyclomatic Complexity.

A measure of the logical complexity of an algorithm, used in white- box testing. D (return to top of page)Data Dictionary.

A database that contains definitions of all data items defined during analysis. Data Flow Diagram. A modeling notation that represents a functional decomposition of a system.

Data Driven Testing. Testing in which the action of a test case is parameterized by externally. See also. Static Testing. E (return to top of page)Emulator. A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system. Endurance Testing.

Checks for memory leaks or other problems that may occur with prolonged. End- to- End testing. Testing a complete application environment in a situation that mimics. Equivalence Class. A portion of a component's input or output domains for which the component's.

Equivalence Partitioning. A test case design technique for a component in which test cases are designed. Error. A mistake in the system under test; usually but not always a coding. Exhaustive Testing. Testing which covers all combinations of input values and preconditions for.

F (return to top of page)Functional Decomposition. A technique used during planning, analysis and design; creates a functional hierarchy for the software.

Functional Specification. A document that describes in detail the characteristics of the product with.

Functional Testing. See also Black Box Testing. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection). Integration Testing.

Testing of combined parts of an application to determine if they function. Events can include shortage of disk space, unexpected loss of communication, or power out conditions. J (return to top of page)K (return to top of page)L (return to top of page)Load Testing. See Performance Testing. Localization Testing.

This term refers to making software specifically designed for a specific locality. Loop Testing. A white box testing technique that exercises program loops. M (return to top of page)Metric. A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code. Monkey Testing. Testing a system or an Application on the fly, i.

Mutation Testing. Testing done on the application where bugs are purposely added to it.

N (return to top of page)Negative Testing. Testing aimed at showing software does not work. Also known as . Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+1.

The cycles are typically repeated until the solution reaches a steady state and there are no errors. Often this is performed using an. Also known as . Multiple accesses to a shared resource. Ramp Testing. Continuously raising an input signal until the system breaks down. 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. Release Candidate. A pre- release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released). S (return to top of page)Sanity Testing. Brief test of major functional elements of a piece of software to determine if. Static Analyzer. A tool that carries out static analysis.

Static Testing. Analysis of a program carried out without executing the program. Storage Testing. Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

Stress Testing. Testing conducted to evaluate a system or component at or beyond the limits of. T (return to top of page)Testability. The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met. Testing. The process of exercising software to verify that it satisfies. IEEE Std 8. 29). May consist of specific.

OS, network topology, configuration of the product under test. This is usually. the smallest unit of testing. A Test Case will consist of information such.

It identifies test items, the features to be tested, the. Ref IEEE Std 8. 29. Test Procedure. A document providing detailed instructions for the execution of one or more test cases. Test Scenario. Definition of a set of test cases or test scripts and the sequence in which they are to be executed.

Test Script. Commonly used to refer to the instructions for a particular test that. Test Specification. A document specifying the test approach for a software feature or. Test Suite. A collection of tests used to validate the behavior of a product. The scope. of a Test Suite varies from organization to organization. There may be several. Test Suites for a particular product for example.

In most cases however a Test.