Monday, September 3, 2007

Integration Testing Solutions for Quality Assurance Teams

QA teams vary in their background and make up. Some QA teams have embraced integration testing. Integration testing veterans have generally approached testing with stubs, harnesses or manual log traces and file dumps. It is a manual, time-consuming process, but it is the only way to access and validate integration data. Other QA teams have been on the boundaries of integration testing and are still focused on the screens and applications. QA teams on the boundaries generally do not have access to the integration layer required to validate integration process flows. For both types of QA approaches, Solstice provides a dramatic improvement in the way business is done.
For QA teams testing their integration manually – the implementation of automated integration testing from Solstice will save substantial time, resources and money. Solstice allows testing teams to access the integration layer for testing. Using an XP-like user interface, Solstice allows testers to capture integration pipes the same way they currently capture and test screens. With a similar test case/test suite paradigm and formatted messages and content, QA teams can accomplish in hours what used to take days and weeks. For QA teams not currently involved in integration testing, Solstice can be a bridge for departments to effectively participate in this increasingly valuable function. Solstice gives QA staff the ability to record and create integration test cases without regular intervention from integration and messaging specialists. Messages tend to be large and complicated, with headers that have little to do with content. Solstice captures both the message and the payload in a familiar XP-like interface that allows testers to see messages on a field-by-field basis. Solstice makes it as simple to test integration as it is to test applications.

No comments:

Counts