The New Economics of SAP Quality Assurance Testing
By: Lynn Shourds,Neil Kosman,Brad Germany
What Creates the C hallenges ?
Real Experience. Real Advantage.
?What Creates the C hallenges
?Mapping the complex relationships between the business processes and the underlying application in order to determine the impact of a change prior to implementing it.
?Managing and validating application upgrades/updates to minimize disruptions and to lower risk.
?Reporting on the progress of lifecycle activities for the extended project team and management.
?Recording and documenting all authorized changes for a complete and detailed audit trail for IT audit and/or compliance initiatives.
Current Model needs to Change
?Manual Testing is a Burden
?Manual Testing can’t keep pace
?No reusability means less coverage
?Time/Turnover causes loss of knowledge
?Multiple skill sets required
?Limited visibility into test coverage
Why Automate SAP Testing?
-Typical lifecycle process required for deploying application
changes is people and time intensive = 2 weeks to 6 months ?
-"One-third of the cost of a package implementation is
being spent on software quality issues, and testing accounts
for 40% of maintenance efforts.”, Thomas Murphy, Gartner
-Be more agile
-Spend less money “keeping the lights on”
-Just in time documentation of business processes
Test Automation–It’s not about quantity
?Your 1000’s of test cases are based on functional / departmental
scenarios, not end-to-end business processes
?Breakpoints and handoffs between functional areas / departments
are where most opportunities for error occur
?Functional / departmental testing does not give a true representation
of the overall flow of business information and business rules
?Automating 1000’s of manual tests will be extremely time consuming
and will not produce a better end result
... to read more articles, visit http://sqa.fyicenter.com/art/