The document discusses the key components and concepts of software testing. It covers people, processes, infrastructure, testing methodologies, test planning and execution, defect tracking, metrics, and more. The core elements of testing include testing strategies, requirements tracing, test case development, test environment setup, test execution, and results reporting. Different types of testing are also outlined such as unit testing, integration testing, functionality testing, and volume testing.

1. The Components of Testing
M
et
ho
do
lo
gy
e
t ur
r uc
To
a st
ol r
s
I nf
Kenneth J. Sweetman
KenSweetman@verizon.net
972 578 9031
1

2. Testing Overview
Testing is the operation of a system or application
under controlled conditions and evaluating the
results (e.g., 'if the user is in interface A of the
application while using hardware B, and does C,
then D should happen'). The controlled conditions
should include both normal and abnormal
conditions. Testing should insure that functionally
works correctly (positive path) and intentionally
attempt to make things go wrong in an application
(negative path).
2

3. Core Elements of Testing
P e o p le P ro c e s s In fra s tru c tu re T e s tin g
 H irin g  O rg a n iza tio n  A rch itectu re  P la n n in g
 T ra in in g  C o m m u n ica tio n  D a ta M o d el  E x ecu tio n
 D ev elo p m en t  P ro ces s F lo w s  N etw o rk  D efects
 E v a lu a tio n  S ta n d a rd s  T o p o lo g y  M etrics
 C o m p en s a tio n  S p ecia l E v en ts  C o n fig u ra tio n  D o cu m en ta tio n
M a n a g em en t
 S k ills I n v en to ry S ta n d a rd s  T es t S ta n d a rd s
 B en ch S tren g t h
3

4. Testing Processes
Test
Management
Requirements Test Test Defect
Traceability Panning Execution Tracking
Environment Application
Management Readiness
 Software Version Control  Load Test Management
 Configuration Management  Network Configuration
 Test Script Version  Test Script Version
 Data Management  Environment Monitor
 Schedule Management  Documentation Control
 Test Automation  Metrics
4

5. Activities
Requirements Traceability Test Execution
Documentation Version Control Standards
Requirement/Test Case Link Workflow
Metrics Metrics
Configuration Management
Test Management
Test Approach – Strategy and Plan
Templates Defect Management
Defined Terms Standards (Priority, Severity, etc)
Standards (Test Folder, Fields, Field Workflow
Values, Required/Optional Fields, etc.) Metrics
Test Build and Maintenance
Testing Standards Committee
Build/Maintain
Standards Management
Schedule
Test Evolution
Validation
Metrics Management
Metrics
Configuration Management
5

6. Roadmap
Summarize and
Report Results
Execute Test
Develop Test Plan
Build Test Scripts
Set Test
Objectives
SDLC
Analysis Design Construction Test Report
& Test
6

7. Metrics – Test Execution
8

8. Metrics – Defects
9

9. Cost of a Defect
10

10. Infrastructure: Configuration Management
C o n fig u ra tio n M a n a g e m e n t
S o ftw a re
- V ersion C ontrol
- S oftw are Inventory
- R untim e C ontrol
- C overage A nalyzer
- T echnical A ssistance
D a ta
- D A S D M anagem ent
- D ata M igration and A ging
- Intraday and N ightly R uns
- R efresh and M aintenance Jobs
- O n D em and Jobs
In fra s tru c tu re
- C onnections to other R egions/A pplications
- E nvironm ent M aintenance and M onitoring
- P roblem D iagnosis and R esolution
- E rror T rack ing(A bends, S ystem D um ps, etc)
- T able M aintenance
- Library S tructures
11

11. Infrastructure: Topology
12

12. Infrastructure: Environment Schedule
Environments "At a Glance"
May June July Aug Sept
3 10 17 24 31 7 14 21 28 2 9 16 23 30 2 9 17 24 31 6 13 20 27
Project A GCX Change 5/15
E24
Release 4.2 TE 1 TE 3
Release 4.3.2 TE 4
Release 4.4 TE 2
GCX Change 5/15
Migration Tools TE 1 TE 3 TE 4
File Delivery TE 1 TE 3 TE 4
GCX Change 5/13
Project B EAB Conflict -- ZQ set to 4/1
Release 1.1 PTE1 PTE 2
Release 1.2 PTE 2
Project C
Release 2.8 TE 1
TE 1 TE 3 TE 4
13 States MQ MQ
Q&R Backend A&B Dev Q&R Backend
TE 2
PTE1 PTE2
DP
SS2 SS2
Tri-state Backend
ZQ Backend ACA Backend
Kenneth J. Sweetman
Environment
13

13. Testing Tools: Configuration Management
H ard w are
Server (Tool Server, W eb Server, etc)
Disk Space
Network
Disaster Recovery
S o ftw are
Tool Set (Defect tracker, Test Script M anagem ent,
Test Execution, Docum ent Control, DB Tools)
Software M anagem ent ( Licenses, Upgrades, Patches, etc)
Database
M onitors
R o les
T e s tin g - Test m anager, test lead, tester, defect m anager,
test autom ation.
E n v iro n m e n t - Software version control, Data M anager,
Configuration m anager, W ebsite M anager.
T o o l S e t - Test tool m anager, DBA, Security adm inistrator,
Tool adm inistrator.
14

14. Business Workflow
Change Policy Points and Register the Loan
15

15. Testing Tools: Deployment
Institutionalization
Deployment
Commitment
Trial Use
Evaluation
Understanding
Awareness
Contact
Time 16

16. Testing – Main Concepts
Black Box Test
 Tests are based on requirements and functionality
 Tests are not based on business processes and not based on
any knowledge of internal design or code.
Known Inputs
Process Known Outputs
White Box Test
 Tests are based on knowledge of the internal logic of an
application's code. Tests are based on coverage of code
statements, branches, logic paths, conditions and data
paths.
Known Inputs
Process Known Outputs
Regression Test
 The re-testing of fixes or modifications to the software or its environment after they have
occurred. Automated testing tools can be especially useful for this type of testing.
 Test critical functions of an application to insure that these functions were not negatively
impacted.
17

17. Testing - Main Concepts
Unit Test
 A preliminary test; to test particular functions or code modules. Typically done by the
programmer and not by testers, as it requires detailed knowledge of the internal program
design and code. Not always easily done unless the application has a well-designed
architecture with tight code; may require developing test driver modules or test
harnesses.
Integration Test
 This is the joint test of each system module. In this phase the components are
integrated and interact in a controled environment. This test is designed to discover
failures and incompatibility between components. The Integration Test completes when
all components have been tested
18

18. Testing - Main Concepts
Functionality Test
The functional specification is used to construct test cases designed to verify each
specified function point (or a “what”) from the user’s point of view. A combination of
positive and negative should be built to reasonably explore the program’s condition set
boundaries.
Usability Test
Is intended to identify usability deficiencies existing in the software. It primarily explores
user interfaces for ease of use and understanding, and for compliance to any specified
usability requirements.
Volume Test
Volume testing involves subjecting the system to heavy volumes of data or work.
Specifically, the system should be able handle the volume of work specified in it’s
objectives. If, for example, one of the objectives is the ability to maintain 100 open files
simultaneously, a test case is generated that opens 100 files and verifies they can be read
from and written to.
19