The 3-Phase Concept for Test Automation

From Manual to Automated

Software testing is conducted to verify that business cases and processes are correctly mapped in the software. Especially in the fields of banking, insurance, telecommunications and public administration, the processes are typically so complex that business domain specialists must participate in the testing process. Such testing can be tedious and time consuming for the client’s business experts, particularly if certain tests need to be repeated. Obviously, finding a way to automate the process would appear to be the ideal solution. Unfortunatey, the know-how of business specalists is frequently only implicit, to mean it has not been documented in writing, and this usually leaves only a few written test cases that could be automated immediately. Thus, our 3-phase concept is a process for converting from manual (oftentimes explorative) testing to automated test execution. To develop this concept for the systematic automation of functional tests, OBJENTIS has leveraged past experience gained on large testing projects. At its core, the 3-phase model relies on a strict orientation to the use cases.

3-phase-concept_1_en

Phase I: Documenting Test Cases by “Twinning”

OBJENTIS experts accompany, or “twin”, the client’s business specialists to document the test cases in writing. The proper structure is ensured by our experts’ methodological know-how, and phase one ends with completion of a test case repository. The repository can be accessed throughout regression testing, thus cutting the time it takes to create new tests. In case of software revisions, this documentation also provides a record for previous testing.

Phase II: Comparing Use Cases and Test Cases

In this phase the test cases are systematically correlated to use cases. On the one hand, this ensures adequate test coverage; on the other, it helps identify redundancies to make them avoidable. The test cases are prioritized, and those found to be redundant or outdated can be removed. The objective is to reduce the testing time and effort, but not without taking into consideration the application risks. At the end of phase two, the use cases already have their test cases assigned, and it takes relatively little technical effort to further process the test cases automatically.

Phase III: Automation

In the last phase, automated test cases are generated from the use cases with inhouse OBJENTIS tools. The test cases can be run with nearly any common automation tool. OBJENTIS experts are available to support clients with the initial implementation of automated testing. Thereafter, the client’s trained staff can efficiently perform regression testing in house.