Software QA

The process of evaluating the products of a given software development activity to determine correctness and consistency with respect to the products and standards provided as input to that activity.

The process of combining software components or hardware components, or both, into an overall system.

(1)The number of independent paths through a program.

(2)The cyclomatic complexity of a program is equivalent to the number of decision statements plus 1.

The test schedule is a schedule that identifies all tasks required for a successful testing effort, a schedule of all test activities and resource requirements.

The process of evaluating a program based on execution of that program. Dynamic analysis approaches rely on executing a piece of software with selected test data.

A manifestation of an error in software. A fault, if encountered, may cause a failure.

1) A discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition; and

2) a mental mistake made by a programmer that may result in a program fault.

1. Testing that employs a test data selection strategy designed to generate test data capable of demonstrating the absence of a set of pre-specified faults, typically, frequently occurring faults.

2. This type of testing allows for designing test cases based on the client specification or the code or both. It tries to identify plausible faults (areas of design or code that may lead to errors). For each of these faults a test case is developed to "flush" the errors out. These tests also force each line of code to be executed

A consistent measure of software size based on user requirements. Data components include inputs, outputs, etc. Environment characteristics include data communications, performance, reusability, operational ease, etc. Weight scale: 0 = not present; 1 = minor influence, 5 = strong influence.

Products, services, or information needed from suppliers to make a process work.

1. Load testing is testing an application under heavy loads, such as the testing of a web site under a range of loads to determine at what point the system response time will degrade or fail.

2. Load testing simulates the expected usage of a software program, by simulating multiple users that access the program's services concurrently. Load testing is most useful and most relevant for multi-user systems, client/server models, including web servers. For example, the load placed on the system is increased above normal usage patterns, in order to test the system's response at peak loads

(1)Testing that takes into account the internal mechanism [structure] of a system or component. Types include branch testing, path testing, statement testing.

(2) Testing to insure each program statement is made to execute during testing and that each program statement performs its intended function.

Structural testing is white box testing, not black box testing, since black boxes are considered opaque and do not permit visibility into the code.

Structural testing is also known as clear box testing, also known as glass box testing.

Structural testing is a way to test software with knowledge of the internal workings of the code being tested.

Closed box testing is same as black box testing. Black box testing a type of testing that considers only externally visible behavior. Black box testing considers neither the code itself, nor the "inner workings" of the software.

Function testing of OO software is no different than validation testing of procedural software. Client involvement is usually part of this testing stage. In OO environment use cases may be used. These are basically descriptions of how the system is to be used.

Bottom-up testing is a technique of integration testing. A test engineer creates and uses test drivers for components that have not yet been developed, because, with bottom-up testing, low-level components are tested first. The objective of bottom-up testing is to call low-level components first, for testing purposes.

or

An integration testing technique that tests the low-level components first using test drivers for those components that have not yet been developed to call the low-level components for test.

Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage.

This type of testing usually requires sophisticated testing techniques.

Comparison testing is testing that compares software weaknesses and strengths to those of competitors' products.

That part of software testing that requires operator input, analysis, or evaluation.

or

A manual test is a test for which there is no automation. Instead, test steps are outlined in a document for the tester to complete. The tester can then report test results and submit bugs as appropriate.