Brainscape's Knowledge GenomeTM

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


See full index

Certified Associate in Software Testing (CAST) > skill category 1 > Flashcards

skill category 1 Flashcards

1
Q

What are some quality control examples?

A
  • writing and executing test cases and scripts
  • participating in both verification and validation activities
  • reporting defects to identify opportunities for process improvement
  • conducting post project reviews
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Quality assurance

A
  • prevent the introduction of flaws
  • implement management quality policies
  • continuous improvement of the software development process
  • proactive approach focused on defect prevention
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Quality assurance examples

A

-defining change control procedures
-analyzing metrics to identify opportunities for process improvement
facilitating quality improvement activities

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

Internal auditing

A

an independent appraisal activity within an organization for the review of operations and is a service to management

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

What is the cost of quality?

A

failure cost + appraisal cost (testing) + Prevention cost

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

Appraisal cost

A

cost associated with the detection of errors

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

Quality control

A
  • detect the introduction of flaws
  • compliance checking
  • proactive approach focused on defect detection
  • testing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Prevention cost

A
  • training
  • establishing methods and procedures
  • tool acquisition
  • cost associated with preventing errors
  • implementing standards
  • planning for quality
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Failure cost

A

cost associated with defective products delivered to customers

  • analyze, correct, and retest defects
  • staffing help desk
  • damage caused by defect
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Analytical school

A

Testing is rigorous and technical

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

Factory school

A

reduction of testing tasks to basic routine or repetitive task

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

Quality (control) school

A

process and standards

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

Context driven school

A

Focus on product and people

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

Agile school

A

continuous delivery of incremental procedures

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

Risk based testing

A

List, prioritize, and test based on the assess risk

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

Structural test

A

test that validate system architecture

-White box testing

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

Functional test

A

test that validate system
-test the overall behavior of the program, by testing transacting flows, input validation, and functional completeness but no knowledge of the internal logic system is used

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

Non-functional test

A 
test that validate system characteristics such as:
performance. 
stability  
maintainability 
usability 
security 
users point of view
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

White box testing

A

structural test technique
-based on knowledge of internal code structure and logic usually -logic driven
-what is the system doing and how is it doing it?
input-> internal view-> output

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

Functional test techniques

A 
requirements
-error handling
-intersystem
-Control
-parallel
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Blackbox testing

A
  • functional test technique
  • testing based on external specifications without knowledge of how the system is constructed-usually data or a business process driven
  • validates the input produces the appropriate output
  • what did the app do? What should it have done?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Blackbox techniques

A
  • equivalence partitioning
  • boundary analysis
  • cause effect graphing
  • all pairs (pairwise testing)
  • State transition testing
  • decision table testing
  • ad hoc or error guessing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Non-functional test types

A
  • accessibility
  • conversion
  • maintainability
  • reliability
  • stability
  • Usability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q 
top down
(incremental testing)
A

testing begins with module highest in the hierarchy using stubs to simulate lower interfacing modules

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

bottom up

incremental testing

A

testing begins with module at bottom of hierarchy using drivers or test harnesses to simulate higher interfacing modules

26
Q

Thread testing

A

often used during the integration of units or components

  • testing a string of units that accomplish a specific function in the app
  • performed with incremental testing
27
Q

Quality

A
  • producers viewpoint: The product meets the requirements

- customers viewpoint: The product is fit for use or meets the customers needs

28
Q

Five perspectives of quality

A
  1. transcendent: i know it when i see it
  2. product based: posses desired features
  3. user based: fitness for use
  4. development and manufacturing based: conform to requirements
  5. value based: Acceptable cost
29
Q 
RAD Model
(rapid application development)
A
  • variant of prototyping
  • form of iterative development
  • designed to build and deliver application prototypes to the client while in the iterative process
30
Q

four phases of RAD

rapid application development

A
  1. requirements planning phases
  2. user design phase
  3. construction phase
  4. Cut over phase
31
Q

Spiral model

A

designed to include the best feature from the waterfall in prototyping and introduces risk assessment

32
Q

Agile practices

A
  • detailed planning: gathering requirements/stories
  • test driven development: test cases written and ran before code
  • refactor relentlessly
  • continuous integration
  • paired programming
  • On site customer
33
Q

Verification

A
  • ensures that the system complies with organization standards and processes, relying on review or non-executable methods
  • Fulfill the requirements
34
Q

Verification examples

A
  • requirements reviews
  • design reviews
  • code walk-throughs
  • Code inspections
35
Q

Validation

A

physically ensures that the system operates according to the desired specs by executing the system functions through a series of test that can be observed and evaluated

36
Q

Validation examples

A
  • unit testing
  • integration testing
  • System testing
  • User acceptance testing
37
Q

Examples of structural system testing

A
  • stress testing
  • execution: System achieves desired level of proficiency
  • recovery: can be returned to an operational status after a failure
  • compliance: Developed in accordance with standards and procedures
38
Q

Product operation

A
  • correctness
  • reliability
  • efficiency
  • integrity
  • Usability
39
Q

Product revision

A
  • maintainability
  • testability
  • flexibility
40
Q

Product transition

A
  • Portability
  • reusability
  • interoperability
41
Q

Major factors that affect testing

A

-people relationships
-scope of testing
-understanding the value of lifecycle testing
-Poor test planning
-Testing constraints

42
Q

Iterative model

A

-project divided into smaller parts
team demonstrates testing earlier on in the process and obtain valuable feedback from system users
-Mini waterfalls

43
Q

Incremental model

A

-subdivide the requirements specifications into smaller buildable projects-Inside the subsets is the waterfall method

44
Q

Waterfall model

A

progress flows downward through the phases of conception, initiation, requirements, design, and construction

45
Q

Defect

A

Undesirable state

46
Q

Process defect

A

Ia test plan standard is not followed

47
Q

Product defect

A

Test plan does not contain a statement of usability as specified in the requirements

48
Q

CMMI

A
  • capability maturity model integration
  • A process improvement model for software development
  • designed to compare in organizations existing development process to prove in best practices develop by members of industry, government, and academia
49
Q

ISO 29119

A

set of standards for software testing that can be used within any software development lifecycle or organization

50
Q

Scope of testing

A

The extensiveness of the test process

51
Q

Optimum point of testing

A

The point where the value received from testing no longer exceeds the cost of testing

52
Q

v model

A
  • waterfall extension

- demonstrate relationships between each phase of specification development and its associated dynamic testing phase

53
Q

ad hoc development

A

relies on the skills and experience of the individual team members performing the work

54
Q

Application lifecycle management

ALM

A

-managing the entire application lifecycle from the initial application definition, through the development lifecycle, to application maintenance and retirement

55
Q

TMMI

A

test maturity model integration

-detailed model for test processes improvement and is positioned as being complementary to the CMMI

56
Q

Lifecycle testing

A

The process of verifying the consistency, completeness, and correctness of software at each stage of the development life cycle
-Verification and validation test

57
Q

Unit testing

A

testing of a single program, module, or unit of code

-Validates that the software performs as designed

58
Q

Integration testing

A

testing of related programs, modules, or units of code

-Validates that multiple parts of the system interact according to the system design

59
Q

Testing schools of thought

A

-a belief shared by a group consist of:

  • analytical school
  • The factory school
  • context driven school
  • Quality (control) school
  • Agile school
60
Q

Requirements

A
  • determine the verification approach
  • determine adequacy of requirements
  • develop test plan
  • Generate functional test cases/database on requirements

Certified Associate in Software Testing (CAST) (6 decks)

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