✨ TESTING
TOOLS
⚠ Problems
to be solved
Manual testing
No time for regression
Set up of test data /
test cases
Ineffective testing
Inadequate test docs
Don't know how much
software has been tested
⏰ When to
select tools
There are not major
panics in progress
Seseorang ada tggungjawab
utk pilih & implement kan
tools tu
Org tak puas hati dgn
current state of testing
practice
Bila ada komitmen drpd top
mgt utk authorize & support
tooling-up effort
✅ How much help
should the tool be?
🔢 Manual execution
of test cases currently
takes 4 person-weeks
🔢 After 3months,
50-60% test case
should be automated,
reducing the execution
time
🔢 After 12 months,
aim to have 80% test
case automated, with
test suite being run in
4 person-days
➗ Division of the tools
in the SDLC V Model
Draw here
🏴 Example
of Test tools
◼: Req Analysis
◼: System Design
◼ Arch Design
◼:Detailed specs
⬜: Softw Validation
⬜ System Testing
⬜ Intgration testing
⬜ Unit Testing
📰 Test Info Mgt
Test Info Mgt Tools ➡
Supports engineers to create,
update and manage info
Test Suite Mgt Tool ➡
Enables engineers to create,
update & manage software
scripts for test execution.
Problem Mgt Tool ➡
Helps engineer bookkeeping
& manage problems during
test process
Test Generation
Tools ✏
White Box : Based on program source code and
structures using program-based test models and
methods, such as the basis path testing technique
Black box : Based on program requirements
using black box test methods, such as random
testing, boundary value analysis methods
Software Simulator
MODEL DRIVEN ➡
simulate the behaviors of a program
process based on a specific model,
such as a finite state machine
DATA DRIVEN ➡
simulate the behaviors of a functional
program based on the given inputs and
return the pre-defined outputs
MESSAGE DRIVEN ➡
simulate the behaviors of a communication
process to generate the protocol-oriented
outgoing messages, based on the pre-defined
incoming messages