Professional Documents
Culture Documents
Software Quality Assurance: Pavithra Subashini
Software Quality Assurance: Pavithra Subashini
Pavithra Subashini
Senior lecturer
Faculty of Computing
Psychology of testing
Why test?
• build confidence
• prove that the software is correct
• demonstrate conformance to requirements
• find faults
• reduce costs
• show system meets user needs
• assess the software quality
Confidence
Confidence
Fault
Faultsfound
found
Time
• A critical process
• Bring bad news (“your baby is ugly”)
• Under worst time pressure (at the end)
• Need to take a different view, a different
mindset (“What if it isn’t?”, “What could go
wrong?”)
• How should fault information be
communicated (to authors and managers?)
Tester’s have the right to:
High
HighLevel
Level Project level (IEEE 829)
Test Plan (one for each project)
Test Plan
check
specification execution recording
completion
Test planning
check
specification execution recording
completion
Identify conditions
Design test cases
Build tests
A good test case
• exemplary
Represents others
• evolvable
Easy to maintain
• economic
Cheap to use
Test specification
check
specification execution recording
completion
Execution
check
specification execution recording
completion
Test recording 1
check
specification execution recording
completion
Check test completion
check
specification execution recording
completion
Coverage
OK
Test completion criteria
Planning Intellectual
one-off
Specification activity Good to
activity automate
Execute repeated
many times
Recording Clerical