Testing Basics Flashcards

1
Q

software engineering

A

systematic development of software

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

5 stages of development

A

Specifications, Design, Implementation, Testing & Maintenance

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

Management Process

A

to Utilize resources, time and money

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

What are management processes

A

Planning, Review and Monitoring

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

To deliver high quality product

A

Software Engineering Principle

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

Time to Market

A

Software Engineering Principle

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

Increasing the Productivity of People

A

Software Engineering Principle

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

It is the testing engineers..

A

who can contribute significantly to the software quality

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

Many projects result in cost overrun or

A

time overrun or both

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

The software must meet all the quality requirements

A

Criteria for the success of a project

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

The software must be development within the time frame

A

Criteria for the success of a project

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

The software must be developed within the budget

A

Criteria for the success of a project

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

The relationship among the team members

A

Criteria for the success of a project

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

The most important requirement of a software product is that

A

it should meet the requirements of a customer

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

Characteristics of a software product can be divided into

A

Operational Characteristics, Transition Characteristics and Revision Characteristics

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

What are operational characteristics?

A

Correctness, Usability, Reliability, Safety and Security

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

What are transition characteristics?

A

Portability, Reusability and Interoperability

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

What are Revision characteristics?

A

Extensibility, Scalability and Maintainability

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

Test engineer needs to understand the..

A

quality requirement of the software to be tested

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

What are quality attributes of a software

A

Operational, Transitional and Revisional characteristics of a software

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

Time

A

To deliver a product within the time frame without compromising on quality

22
Q

A software project is considered a success when

A

software meets the quality standards within time and budget and the execution goes smoothly without affecting the human relations

23
Q

Test engineers should offer constructive criticism by suggesting how the software can be improved rather than just doing fault finding

A

Managing the relation between development and testing teams

24
Q

Defines the various steps to be followed to convert the raw material into the finished product

A

PROCESS

25
Q

Take the problem definition as an input and produces the software product

A

Software Process

26
Q

Divided into various phases and in each phase a set of activities is carried out to arrive at the end product

A

Process of software development

27
Q

Each phase in software development will have a

A

defined input and a defined output

28
Q

Whether the solution considered to accomplish the requirements is practical and workable

A

feasibility study

29
Q

Requirements of the client are obtained, analyzed, documented and validated

A

Requirements Engineering/Requirements Gathering phase

30
Q

Inputs and Outputs of Requirements Engineering Phase

A

Problem Definition and SRS document

31
Q

Input and Output of an implementation process

A

design document and source code

32
Q

Metrics is also called

A

quantitative measures

33
Q

SQA

A

Software Quality Assurance - ensures process definitions are followed strictly by the development teams

34
Q

The effort for execution of a project is measured in

A

person month

35
Q

72 PM

A

6 people work on a project for 1 year

36
Q

Different CMMI Maturity Levels

A

Initial, Managed, Defined, Quantitatively Managed, Optimzing

37
Q

What is the method to attain continuous improvement

A

Plan your work, Track your Work and Analyze your work

38
Q

Testing the process to prove that the software doesn’t work correctly

A

Psychology of Testing

39
Q

To ensure that the software meets the requirements of a customer

A

Validation

40
Q

To ensure that the software conforms to specifications

A

Verification

41
Q

Are we building the product right

A

Verification

42
Q

Are we building the right product

A

Validation

43
Q

Objective of testing

A

is to uncover as many bugs as possible

44
Q

Three components of cost of quality

A

Failure Cost, Appraisal Cost and Prevention Cost

45
Q

When is testing complete

A

When you run out of time, run out of money or when you meet the exit criteria

46
Q

Constructive criticism

A

Test engineers need to provide constructive criticism to improve the quality of the software rather than finding fault with the developers

47
Q

In this testing, the structure of the program is not considered at all

A

Black box testing

48
Q

Statement coverage, path coverage, branch coverage is considered in

A

White box testing

49
Q

Testing that decides whether the client approve of the product or not

A

Acceptance testing

50
Q

A set of input parameters for which the software will be tested

A

test cases