Month: August 2012

Software Testing Dictionary – 6

Latent bug A bug that has been dormant (unobserved) in two or more releases. [R. V. Binder, 1999] Lateral testing. A test design technique based on lateral thinking principles, to identify faults. [Dorothy Graham, 1999] Limits testing. See Boundary Condition testing. Load testing Testing an application under heavy loads, such as testing a website under a range of loads to determine at what point the system’s response time degrades or fails. Load Stress test. A test is designed to determine how heavy a load the application can handle. Load-stability test. Test design to determine whether a Web application will remain Read More

Software Testing Dictionary -5

High-level tests. These tests involve testing whole, complete products [Kit, 1995] Inspection A formal evaluation technique in which software requirements, design, or code are examined in detail by a person or group other than the author to detect faults, violations of development standards, and other problems [IEEE94]. A quality improvement process for written material that consists of two dominant components: product (document) improvement and process improvement (document production and inspection). Integration The process of combining software components or hardware components or both into an overall system. Integration testing – testing of combined parts of an application to determine if they Read More

V Model

V & V PROCESS MODEL :  V&V Model is Verification & Validation Model. In This Model, We work simultaneously on Development and Testing. In this Model One V for Verification and one For Validation first ‘V,’ we follow SDLC(Software Development Life Cycle), and Second ‘V’ we follow STLC-(Software Testing Life Cycle).  Testing normally done in a large system in 2 parts. The functional verification and validation against the Requirement specification and Performance evaluation against the indicated requirements.  Testing activity is involved right from the beginning of the project. The use of the V&V process model increases the rate of success Read More

Software Testing Dictionary -1

Acceptance Test: – Formal tests (often performed by a customer) to determine whether or not a system has satisfied predetermined acceptance criteria. These tests are often used to enable the customer (either internal or external) to determine whether or not to accept a system. Ad Hoc Testing: – Testing carried out using no recognized test case design technique. [BCS]   Alpha Testing: – Testing of a software product or system conducted at the developer’s site by the customer.   Artistic Testing: – Also known as Exploratory testing.   Assertion Testing. (NBS)A dynamic analysis technique that inserts assertions about the relationship Read More

Software Testing Dictionary -4

  Failure: A failure is a deviation from expectations exhibited by software and observed as a set of symptoms by a tester or user. A failure is caused by one or more defects. The Causal Trail. A person makes an error that causes a defect that causes a failure.[Robert M. Poston, 1996]   Fix testing. Rerunning of a test that previously found the bug in order to see if a supplied fix works. [Scott Loveland, 2005]   Follow-up testing, we vary a test that yielded a less-than-spectacular failure. We vary the operation, data, or environment, asking whether the underlying fault in the Read More

Software Testing Dictionary -3

    End-to-End testing. Similar to system testing; the ‘macro’ end of the test scale; involves testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.   Equivalence Partitioning: An approach where classes of inputs are categorized for product or function validation. This usually does not include combinations of input, but rather a single state value-based by class. For example, with a given function there may be several classes of input that may be used for positive testing. If Read More

Software Testing Dictionary -2

  Data-Driven testing An automation approach in which the navigation and functionality of the test script is directed through external data; this approach separates test and control data from the test script. [Daniel J. Mosley, 2002]   Data flow testing Testing in which test cases are designed based on variable usage within the code.[BCS]   Database testing. Check the integrity of database field values. [William E. Lewis, 2000]   Defect The difference between the functional specification (including user documentation) and actual program text (source code and data). Often reported as a problem and stored in defect-tracking and problem-management system   Defect Also called a Read More