QAHeaven.

com
Software Quality Assurance & Testing (SQAT)
Always test so whenever you need to stop you have done the best positive testing

SQAT – Provides information to unambiguous

assure the quality of: the product, verifiable Test Roles
decisions, process Test leader
Risk - the chance for something (manager)
Test policy to include: unwanted to happen. test analyst/designer
Definition of testing Risk Level: probability x for a test executer,
test process to use, certain event to take place à reviewer/inspector
test evaluation ideally, 0
quality targets Tester skills:
test process Test Levels: Testing skills
improvement activities acceptance testing (user, IT skills
operational (OAT) Domain knowledge
Test Strategy to consider when contractual (CAT - alpha Soft skills
planning: and beta)
standards to use System testing The best team has following
risks to address integration testing members type:
levels of testing entry/exit (modules, systems) Advocate
criteria modular testing Coordinator
techniques to use, Assessor
reuse Test estimation techniques: Concluder
environments Intuition Expert
automation, Metrics used before, Executor
measurements, Experience
regression testing Successful creative team
Test plan must have: roles:
Development models: Introduction Identity
Sequential RDCT* test items Purpose
Waterfall and V Model features to be tested/not Feedback
RDCTT to be tested Growth
Iterative & Incremental: approach Tolerance
Agile. Item pass/fail criteria Comfort
suspension criteria Diversity
Risk management: test deliverables Awareness &
risk identification testing tasks creativity
risk analysis environmental needs
risk mitigation responsibilities Bug tracking support:
staffing and training Bugzilla
QA Paradigms**: schedule Jira
mainframe risks HP Quality Center
simple systems
composite systems, Test types:
critical systems A plan must be: S.M.A.R.T Functional
in-house, Specific Non-functional
PC-based Measurable Structure/architectur
client-server Agreed e.
web-based Relevant Change related:
embedded Time specific confirmation testing
regression testing
Requirements must be: Test environment: maintenance testing
attainable Hardware of existing products
modifiable Software
complete Network Validation* - did we make
necessary Data/Tools the right thing?
consistent, Training classes

*RDCT – Requirements, Design, Coding, Testing

**QA Paradigms – types of systems for testing
QAHeaven.com
Verification** - did we make the Each team members must
thing right? do a GET on Source Cause of defects:
Code at the beginning of human error
Test process for all test levels: each day to ensure they misunderstandings
have the latest code wrong assumptions
Test Planning Each team member must complexity
enter their time daily time
(time worked and mental overload
estimated hours
Analysis&Design remaining). Test process assessment
Each team member must models:
attend the Daily Scrum CTP – critical
Meeting (or have a testing process
Implementation & representative present). STEP – Systematic
execution Each team member must Test & Evaluation
check the Daily burn- Process
down (for dev and qa) TOM – Test
such that deviations can Organization
Evaluation & be observed/treated on Maturity
Reporting time. SQR – Software
quality Rank
Test Cases:
must be created before Test Procedure must
Monitor & Control coding begins on any include:
feature. unique ID
must be run by the description
programmer before explicit precondition
Bug/Incident Reporting: releasing the code for for start
Summary inspection. included test cases
Severity (Source: in execution order
Project ww.softwareplanner.com) post conditions
Module traces
Environment Test Case Design Techniques
Steps to reproduce Degree of independence in
expected result Behavior based Testing:
actual result Equivalence partitioning 1. producer tests own
logs Boundary value analysis product
notes Decision tables and cause 2. peer tests the product
reproducible status effect 3. testing done by tester
show stopper (Y/N) State transitions on team
found in Use cases 4. test by test team
Structure based 5. external consultants
Agile Statements advice
Scrum Team – no more 7 Decisions 6. testing is outsourced
resources per team Conditions
Engineering Manager Loops Requirements must be:
Scrum Master Paths attainable
Software Development Experienced based consistent
and Quality Assurance Error guessing complete
team Check lists necessary
Business Analyst Exploratory modifiable
Attacks unambiguous
Scrum Rules Defect based testable
The ScrumMaster is responsible for Taxonomies
the following: Fault injections
Each team member must Random
check their code in daily
(or when it is compilable).

2
QAHeaven.com

Product risks:
originate from the
development process
requirements
design
code

Validation of requirements:
walk through
review
role play
usability assessment
acceptance testing Test case, Test design, Risk levels,
RDCT, V Model, Requirements, Test
Types of testing: levels, Estimation techniques,
Acceptance testing – done S.M.A.R.T, Bugzilla, Functional
against user requirements testing, Non-functional testing,
System integration test – Regression testing, Confirmation
done against product testing, Doc reviews, Agile Scrum
design Teams, Scrum Rules, Test Assessment
System test – done against models, Cause of defects, Validation,
Verification, Product risks,
system requirements
Acceptance testing, System
integration testing, System test,
Verification of requests – done Dynamic testing, Component testing
by:
dynamic testing
acceptance testing
system integration testing
system testing
component integration
testing
component testing

Requirement management
process is content driven:
Obtain understanding and
commitment
Maintain bidirectional
traceability
Monitor requirements
implementation
Manage requirements
changes
Requirements are always
relevant