Brainscape's Knowledge GenomeTM

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


See full index

125 software engineeringg > Testing > Flashcards

Testing Flashcards

1
Q

software quality

A

desirable attributes of software products

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

8 product quality model

A 
functional suitability
performance efficiency
compatibility
usability
reliability
security
maintainability
portability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

software testing

A

investigation conducted to provide info about the quality of the software product

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

correctness

A

perform exact tasks

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

robustness

A

react appropriately to abnormal condition

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

reliability

A

degree to a software behaves robustly overtime

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

reliability measurement

A 
metrics:
  mean time to failure
  mean time to repair
  mean time between failure
  rate of occurrence of failure
  probability of failure on demand
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

causes to reliability problems

A

incomplete testing, require

require changing during dev

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

software error terms

A

fault/ defect / bug/ flaw:

failure: unexpected run-time behavior observed by the user of the system

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

failure with

A

syntax fault
run time
logic

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

RIP model

failure determination

A

reachability: location
infection:
propagation: cause some incorrect output of program

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

failure categories

A 
transient occurs only with certain input
permanent
recoverable
unrecoverable: sys recovery need to have operator intervention
non-corrupting
corrupting data
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

verification in testingq

A

static : code

dynamic: run with test data

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

exhaustive test

A

produce all possible combination of input data values and compare outputs

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

testing golden rules

A

maximize the number and severity of defects found per dollar spent
only presence of error

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

black box testing

A

having no knowledge of how the code works

-> input and expected output

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

black box strategy

A

boundary value
equivalence partitioning
cause and effect graph

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

black box deficiencies

A

can not detect dead code
dead code : identified through profiler
can miss non-terminating loop

19
Q

fuzzing testing

A

blackbox testing

huge input random/ malformed data

20
Q

white box

A

full knowledge of program code
desgin test will make the program run every statement at some point
path testing

21
Q

black box

A

requirement, can be done early

22
Q

white box

A

implementation, expensive and lengthy

23
Q

gray box

A

white box: study and gain understanding of the internal features of the app
design and define test cases
black box

24
Q

testing methodology

A

fuctional test: unit, integration, sys, acceptance

non-func: performance, security, usability, compatability

25
Q

unit testing

A

checking function of individual units/ components
isolation
white box

26
Q

test drive

A

driver contains just enough code and data to call the unit to be tested

27
Q

test stubs

A

module place holders to stimulate (not yet implemented)

28
Q

integration test

A 
checking interfaces and flow of data/information among individual units/components
 \+ function
 \+ parameter types
 \+ params value
 \+ function performance
29
Q

Inter test

Big-bang approach

A

all components are tested same time

30
Q

inter test

top-down approach

A

start from the top

31
Q

Top-down

A

Cons:

lower level modules are tested last

32
Q

Integration test - bottom-up approach

A

start from bottom

33
Q

Hybrid approach

A

top-down + bottom up

start from the middle layer

34
Q

System test

A

end to end test

meet specified requirements

35
Q

Acceptance test

A

whether it is acceptable for delivery

36
Q

Regression test

A

re-executed to verify the impact of software changes

37
Q

functional smoke test

A

performed critical functionalities of the program are working fine

38
Q

functional sanity test

A

after a software minor changes

39
Q

non-functional test

A

performance, usability

40
Q

security testing sample checklist

A

authentication, authorized, password, time out, data backup, data protection

41
Q

performance testing sample checklist

A

the response time
throughput
process time
increasing load

42
Q

test documents - types

A

policy, strategy, plan, requirments, case, scenario…

43
Q

Software testing life cycle

A

strategy -> development -> execution -> management -> delivery

44
Q

test plan

A

set of guiding principles
Project scope
testing scheduling
testing resource

125 software engineeringg (5 decks)

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