Given that SOA breaks up the traditional application into loosely coupled units of work and BPM ties these units together to execute a complex series of transactions, the way we test a BPM environment is totally different than testing a traditional application.
First, we need to place bracers around the business assumptions held in the units of work. Meaning it is the job of the total development staff to be able to tell us if the business assumptions held within the unit of work are valid. The level of test or regression validation will allow organizations to enter into a phase of change based testing. Change based testing focuses on validating business processes in the face of changing units of work. Furthermore, we need to shift the focus of QA from the traditional "testing" to more of an audit. QA should be auditing the business process much like the way a CPA firm audits the financial statements of an organization.
Dig Deeper on Topics Archive
Related Q&A from Rami Jaamour
Rami Jaamour discusses how to go about planning on using emulation in order to simplify complexity or replicate the behavior of systems that are ... Continue Reading
Rami Jaamour discusses the best place to begin when building a testing system for SOA and how to establish a quality policy as part of the overall ... Continue Reading
Rami Jaamour suggests business process simulation and business process testing for optimizing BPM and realizing the ROI. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.