Testing Definitions Flashcards Preview

Interview Prep > Testing Definitions > Flashcards

Flashcards in Testing Definitions Deck (53):
1

Testing carried out by the client to accept the software

Acceptance Testing

2

Testing carried out to ensure that the software can be used by the physically challenged person

Accessibility Testing

3

Testing done without any defined process

Ad-hoc testing

4

To verify that the software development is carried out as per a defined process

Audit

5

Testing carried out with minimal manual intervention

Automated Testing

6

Portion of software in which there are no branches

Basic Block

7

Baseline

First version of a work product

8

Testing carried out on a software product at the user's site in the absence of development team

Beta testing

9

Testing carried out to check the functionality of the software

Black box testing

10

A Bug

A colloquial term to indicate defect in software

11

Software Development Organizations are graded based on the process maturity

Capability Maturity Model

12

A list that is used to check whether the requirements are met

Checklist

13

Defect classification is done based on

severity and priority of defects

14

Number of defects found per 1000 lines of code and number of function points

Coding Metrics

15

Testing to ensure compatibility with different hardware platforms

Compatability testing

16

A systematic procedure to make changes to any work products such as SRS, source code, etc.

Configuration Management

17

To remove the defects reported by clients

Corrective Maintenance

18

Number of defects per 1000 lines of code

Defect Density

19

A technique used to ensure that the software doesn't fail even if wrong inputs are given

Defensive programming

20

Architecture of the software is worked out in what phase

Design phase

21

Equivalence class partitioning

method used for selecting the test cases. test cases are chosen based on valid inputs and invalid inputs

22

Testing the values on the boundary

boundary value analysis - a testing method

23

Testing carried out by all possible inputs

Exhaustive testing

24

Testing carried out in the actual working environment

Field Trial

25

Testing carried out to test the functionality of the software

functional testing

26

The chart that gives the various project activities with start and end dates and is used to monitor the progress of a project

Gantt chart

27

Testing carried out while combining different modules of a software package

Integration testing

28

A testing carried out to see how system behaves under certain load condition

Load Testing

29

Independent entity in a software

Module

30

Non functional requirements

Performance, security, reliability, portability, usability

31

OOA, OOD, OOP, OOT

Object oriented analysis, design, programming, technology

32

The source code that's freely distributed by the author

Open source software

33

Sub-contracting of specialized work

Outsourcing

34

Reviews carried out by peers or persons at the same level in the hierarchy

Peer Review

35

Testing carried out for normal, peak and exceptional load conditions.

Performance testing

36

The ease with which a software package can be transferred from one platform to another

Portability

37

To make changes in the software anticipating some defects in particular environment

Preventive Maintenance

38

A step by step procedure to convert a raw material into a finished product

Process

39

What's measured in terms of MTBF

Reliability of a software

40

Testing carried out to ensure that modifications of one portion of software have no bad effects on other portions of the software

Regression testing

41

An uncertain outcome

risk

42

Identifying the possible risks and taking preventive/corrective actions

Risk management

43

A quick and dirty testing is also called

Smoke testing

44

Systematic development of software

Software engineering

45

A step by step procedure to convert a problem definition into a working software product

software process

46

A document that captures the requirements of the proposed software

Software Requirements Specifications

47

Testing done at or beyond the limits of specified requirements of performance to check where the software fails

stress testing

48

Source code is looked into for testing. Every line of the code is tested

Structural testing

49

After all the modules are combined together, testing carried out on the total system. Testing done after integration testing and before acceptance testing

System testing

50

A set of input parametersfor which the software will be tested

Test cases

51

A document that gives the detailed plan for testing the systems and the testing process

test Plan

52

To check whether the software meets the customer expectations. Are we building the right product

Validation

53

To check whether the software conforms to specifications. Are we building product right

Verification