Please enable JavaScript.
Coggle requires JavaScript to display documents.
SOFTWARE TESTING (Roles (Test manager, Test lead, Test analyst, Test…
SOFTWARE TESTING
Object Under Test
Preconditions
Stimuli
Actual behavior
Expected behavior
Roles
Test manager
Test lead
Test analyst
Test designer
Tester
Automation developer
Test administrator
Testing levels
Unit testing
Verify the functionality of a specific section code
Integration testing
Expose defects in the interfaces and interaction between integrated components
System testing
Verify that the system meets its requirements
Operational acceptance testing
Non-functional software testing
Testing approach
Static, dynamic and passive
Static
Performing software without actually executing programs
Involves verification
Review, walkthroughs, inspections
Dynamic
Test particular sections of code when the software itself is run
Involves validation
Execution of a debugger enviroment
Passive
Verifying the system behavior without any interaction with the software product
Runtime verification and log analysis
Exploratorie
Simultaneous learning, test design and test execution
What the software does and what it does not do
The "box"
White-box testing
Verifies the internal structures or workings of a program
Can be applied at the unit, integration, and system levels
Black-box testing
Examining functionality without any knowledge of internal implementation
Use case testing and exploratorie testing
Grey-box testing
Requirements
Functionals
Non-functionals
Testability
Scalability
Maintanability
Shows the ability to update or modify the system under test
Performance
Verifies if a system claims manufacturer made specifications
Security
It is essential for software that processes confidential data to prevent system intrusion by hackers
Authorization
Authentication
Confidentiality
Integrity
Availability
Non-repudation
Testing Process
Traditional waterfall development model
Agile or XP development model
A sample testing cycle
Requirements analysis
Test planning
Test development
Test execution
Test reporting
Test result analysis
Defect restesting
Regression testing
Test Closure
Test types
What tests
When tests
Why tests
Who tests
Where tests
How tests
How well tests
Testing artifacts
Plan
Includes aspects such as objectives, scope, processes and procedures, personnel requirements, and contingency plans
Matrix
It is a table that correlates requirements or design documents to test documents
Case
Consists of a unique identifier, requirement references from a design specification, preconditions, events, a series of steps (also known as actions) to follow, input, output, expected result, and the actual result
Script
It is a set of instructions that will be performed on the system under test to test that the system functions as expected
Suite
A collection of test cases
Data
All the test values and changeable environmental components are collected in separate files and stored as test data
Harness
It is a collection of software and test data configured to test a program unit by running it under varying conditions and monitoring its behavior and outputs