Making Software Testing Work
Quality Assurance &
Software Testing Methodology
Presentation to JPMorganChase
Making Software Testing Work
Contents







What is ATS
What is PLP Methodology
Our Differentiators
Accomplishments
Benefits
Why Amtex
Recap
Making Software Testing Work
Application Integration Testing
System Integration Testing
Making Software Testing Work
Business Testing or Quality Assurance Phase
Engineering Testing or Quality Control Phase
Testing Overview
ATS
 We work with & act as Business Users, while bringing a structured
approach to testing.
 Our testing practice includes: Test Strategy Definition, Test Plan
Creation, Test Case Writing, Test Execution and Certification that
requirements have been met.
 With our proven onsite/offshore delivery model, Software Testing is
a cost-effective approach to reducing ROI for clients.
Making Software Testing Work
Testing Scope
ATS
 Business Testing under ATS is focused on two major issues
though very often both are confused with same objective
 System Integration Testing
 System Integration Testing is focused on the technical
infrastructure e.g. messaging, data flow, interfaces, and tools
that are critical for application’s and systems to work. Less
stress on application functionality unless necessary.
 Application Integration Testing
 Also referred as Functional Integration Testing (FIT)
 Focused on application flow and functionality. Typically
tested through a set of test plan / scenario each depicting a
business process flow. Each plan / scenario may consist of
several steps called test cases.
Making Software Testing Work
System Integration Testing




System Integration Testing is focused on the technical infrastructure
like messaging, data flow, interfaces, and tools that are critical for
application to work. Less stress on application functionality unless
necessary.
For smaller applications or where such points of testing are small in
number or non-critical, then SIT can be merged with AIT for effective
test resource utilization.
The test strategizing involves identifying points of testing:
 Not every data flow is meant to be tested as application flow will
test the data flow. The stress on data flow is through utilities and
tools like an extractor, uploads from spreadsheet data, etc.
 Similarly in messaging, testing is done on whether formats are
right, complete and message flows across modules / systems
 If there are tools used, then test the tools from their utility to
application.
In short, we need to identify points of testing without getting caught up
with the entire application. We call this methodology ‘Dot-The-Map’.
Making Software Testing Work
Dot-The-Map Methodology
 Dot-The-Map methodology is developed uniquely by Amtex for
System Integration Testing.
 Focus is emphasized on isolating the points of testing (‘Dots’) that
are critical for testing.
 A crucial criteria is whether such dots see the application as black
box and vice versa – or else the testing must be combined with
AIT
 Examples,
 In applications that use MQ series messaging, testing message
structure, flow, message servers.
 In applications that use SWIFT messages (MT 101, MT103…),
testing message formats, completeness and flow rather what
application does with the messages when they come right.
 Testing tools – e.g., a converter that converts EBCIDIC files to ASCII
‘Dot-The-Map’ Methodology – Pick the critical points that tie the application together.
Making Software Testing Work
Methodology



Check & Dig - The test plans and cases are written from a simple link
(task) flow. For each link there are many combinations of flows. From
domain knowledge, choose flows for testing that are different. If defect
is found, choose more permutations & combinations. A selective and
pragmatic approach to find errors and explore error zones.
Each stage of testing - FIT, UAT, OAT - focuses on a select objective.
Automated Testing tools like Win Runner, Load Runner and Test
Director are used when the application is ready for a multiple roll out.
2 different logic
in flows - Check
both.
All possible flows
are identical in
logic - Test one
flow.
Task 1
Task 2
Task 3
Business Process Flow
Making Software Testing Work
Key Differentiators
Testing Methodology basics haven't changed, but
applications have grown in size and technology
complexity. ATS brings in unique ‘PLP’ and ‘Dot-TheMap’ methodologies for effective use of testing efforts.
Amtex compliments technical depth with excellent
domain knowledge by using Business Analysts to
provide ‘what is the right application’ perspective to
testing.
Right Methodology is a critical
success factor for for
effective use of efforts.
For Business applications
domain expertise of team is a
necessity.
Automation is inevitable in
most banking applications
with multiple releases
Automation testing is viable and cost effective and we
have technical resource pool with automation experience
on banking applications.
[Mercury / Rational / Compuware]
We act like certifier than consultant. We don’t merely
execute testing services - We assure
‘fit for use’.
Testing Business Applications
is both about ‘Is application
RIGHT for use?’ and ‘Is
application working?’
Amtex has a matured process and methodology to
offshore significant workload & bring down costs.
Making Software Testing Work
We have effectively done test
planning/scripting and
execution offshore
PLP Methodology
Engagement Models
OAT
All Technology and other assumptions
made during the entire cycle must be
verified before the application is online
UAT
Business users (end-users) must have a
feel of the software and sure of its ability
to deliver their expectations
FIT
End-to-end functional integration testing
to ensure process flow as envisaged in the
application software requirement
Unit, module and
SIT
Typically done by the development team
to confirm they have done a right coding.
SIT ensure messaging conformance and
data flow across units
Review
BR,FS, DD
Building Quality begins here where
unambiguous and complete
documentation is vital for right execution
Trust, But
Verify before
Going online
Building
business-user
Confidence
First
Comprehensive
end-to-end testing
Base Level
Quality Checks
to move forward
Gap analysis
&
Traceability Matrix
Making Software Testing Work
A complete 3rd
party testing of all
phases post
development
ensures excellent
cost savings as
successive phases
can leverage on
knowledge gained
on application
Engagement in a
any specific
phase still gives
the best of
SakAssure - With
Domain
knowledge in FIT
or Technical
depth in OAT
Benefits
 We combine the requisite domain knowledge & technical skills
to make business testing a success
 We compliment your team of business users and bring in
structured & detailed testing process knowledge
 Our ‘PLP’ methodology is efforts-effective
 We bring down costs with proven offshore model
 We have the necessary background and excellent credentials
Making Software Testing Work
Why Amtex
Focused Resource



Deep domain skills
 Business Consulting Group
 Wide range of solutions spanning all segments of banking and retail
lending
Experienced software services company
 Full service provider of IT Outsourced solutions
– Custom Application Development
– Application Testing
– Staff Augmentation
 Extensive project management and technical capabilities
 Flexible, dependable, scalable and cost effective
Committed to provide the highest quality
 ISO9001:2006 certified Quality Management System
Making Software Testing Work
Trusted Partners
Why Amtex
CITIGROUP
Information Builders
Testing Methodology and Automation
Functional Testing & Test Management
Full testing Lifecycle
Complete Testing Outsource for all
Global Application Deployment
HARRISONS GROUP
myCove.com
SDLC Development
Testing Best Practices
Legacy Systems Conversion
and Automation
Making Software Testing Work
Why Amtex
Technology Breadth
 Technology Labs
 Test Lab: Tools expertise on Mercury (Win Runner, Quick Test Pro, Load Runner, Test
Director, Astra Load, Web Load), Rational and Compuware
 BI Lab: Data Warehousing & Business Intelligence products and tools expertise including
Informatica, Oracle Warehouse Builder, SQL Server DTS, Business Objects, Hyperion,
Cognos, MicroStrategy, SAS
 Base Technology Practice
 Java Practice: J2EE, JSP, EJBs, Servlets, JDBC, etc.
 Microsoft Practice: .NET, VB, VC++, COM/DCOM, IIS, MTS, ASP, etc.
 Mainframe Practice: MVS, CICS, Cobol, VSAM, DB2, CoolGen, MQ Messaging
 Other Skills: Cold Fusion, Power Builder, BPwin, etc.
 Extended Technology Groups
 Database Group: Oracle (including OLAP Services), MS SQL Server (including Analysis
Services), Sybase, DB2, MySQL
 OS Group: Windows 2000, Unix flavors like Solaris, AIX, Linux, Mainframes & Macintosh
 Middleware Group: Web Sphere, Jrun, JBOSS, Oracle 9i Application Server, Web Logic,
Pramati, Apache
 Data Modeling Tools: ERwin, Oracle Designer, Rational
Making Software Testing Work
Recap
Amtex Systems Has:
• Domain knowledge
• Technical skills
• Credentials
• Methodology
• Cost Advantage
“To make Business Application and System Testing a Total Success.”
Glossary of Terms & Acronyms:
PLP Process Link Probe
AIT Application Integration Testing
ATS Amtex Testing Service
FIT Functional Integration Testing
OAT Operations Acceptance Test
SIT System Integration Testing
UAT User Acceptance Testing
ROI Return On Investment
BR Business Requirement
FS Functional Specification
DD Design Document
Making Software Testing Work