Testing FAQ

Questions about Automated VC Model Testing

Raising the bar on how modeling and release teams create and maintain configurable product models and data is a focus for eSpline’s products and services.

The ConfigScan Automated VC Testing solution is a standalone testing application that attaches to your SAP system where you build your test cases once and use them many times. The test cases are integrated into the eSpline Avenue Managing VC solution where you can view the product model, document it, compare two models for differences and submit the model for a health check.

"Can you reduce the staff hours we spend today on manual testing?"

Yes. The ConfigScan automated testing solution enables a “write once, run many times” technique for test cases, such that the labor hours you now invest in manual testing are instead applied to creation of a suite of regression-preventing test cases. You’ll recover the investment in building the test case library the very first time it is run.

“Can we increase test coverage and quality via automatic testing?”

Yes, the time saved by automatic testing frees your staff to focus on adding more tests, troubleshooting, and repairing defects as they are uncovered.

"Is there an economical way to test more frequently?

We currently only test manually before our most significant events such as release of a new product, or major changes to an existing product We’d like to test all productive changes to our product models, instead of waiting for our customers to discover problems?"

Yes, definitely. The cost of automatically running an existing library of test cases is negligible compared with equivalent manual testing. So you can run your tests a) more frequently: not only before a major release, but before a minor or patch release, b) after a single change or set of changes by a single modeler as a unit test of his or her changes. Catching defects earlier in your build and release process reduces the cost impact of each defect.