Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Test Analyst Interview > Testing Definitions > Flashcards

Testing Definitions Flashcards

1
Q

Testing carried out by the client to accept the software

A

Acceptance Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

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

A

Accessibility Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Testing done without any defined process

A

Ad-hoc testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

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

A

Audit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Testing carried out with minimal manual intervention

A

Automated Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Portion of software in which there are no branches

A

Basic Block

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Baseline

A

First version of a work product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

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

A

Beta testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Testing carried out to check the functionality of the software

A

Black box testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

A Bug

A

A colloquial term to indicate defect in software

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Software Development Organizations are graded based on the process maturity

A

Capability Maturity Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

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

A

Checklist

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Defect classification is done based on

A

severity and priority of defects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

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

A

Coding Metrics

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Testing to ensure compatibility with different hardware platforms

A

Compatability testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

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

A

Configuration Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

To remove the defects reported by clients

A

Corrective Maintenance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Number of defects per 1000 lines of code

A

Defect Density

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

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

A

Defensive programming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Architecture of the software is worked out in what phase

A

Design phase

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Equivalence class partitioning

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Testing the values on the boundary

A

boundary value analysis - a testing method

23
Q

Testing carried out by all possible inputs

A

Exhaustive testing

24
Q

Testing carried out in the actual working environment

A

Field Trial

25
Q

Testing carried out to test the functionality of the software

A

functional testing

26
Q

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

A

Gantt chart

27
Q

Testing carried out while combining different modules of a software package

A

Integration testing

28
Q

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

A

Load Testing

29
Q

Independent entity in a software

A

Module

30
Q

Non functional requirements

A

Performance, security, reliability, portability, usability

31
Q

OOA, OOD, OOP, OOT

A

Object oriented analysis, design, programming, technology

32
Q

The source code that’s freely distributed by the author

A

Open source software

33
Q

Sub-contracting of specialized work

A

Outsourcing

34
Q

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

A

Peer Review

35
Q

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

A

Performance testing

36
Q

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

A

Portability

37
Q

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

A

Preventive Maintenance

38
Q

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

A

Process

39
Q

What’s measured in terms of MTBF

A

Reliability of a software

40
Q

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

A

Regression testing

41
Q

An uncertain outcome

A

risk

42
Q

Identifying the possible risks and taking preventive/corrective actions

A

Risk management

43
Q

A quick and dirty testing is also called

A

Smoke testing

44
Q

Systematic development of software

A

Software engineering

45
Q

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

A

software process

46
Q

A document that captures the requirements of the proposed software

A

Software Requirements Specifications

47
Q

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

A

stress testing

48
Q

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

A

Structural testing

49
Q

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

A

System testing

50
Q

A set of input parametersfor which the software will be tested

A

Test cases

51
Q

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

A

test Plan

52
Q

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

A

Validation

53
Q

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

A

Verification

Test Analyst Interview (35 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions