Automated Software Tests in the SAP Environment
Highly integrated enterprise software such as SAP is subject to continuous changes in its life cycle – due to company mergers, changed legal requirements, new technologies, or simply upgrades and service packages. Of course, adjustments to the system have to be tested. Ideally, at the touch of a button. But is this type of automation possible and desirable?
Due to regular release cycles, regression tests are one of the most important types of testing in the SAP environment. They can help establish whether a function that worked perfectly in a previous version continues to work in the new release. In addition, automation can speed up the testing and evaluation processes overall, because regression test cycles are not linked to the availability of user departments, who can then be relieved of recurring – and time-consuming – routine testing.
To find out which parts of a software solution must be tested repeatedly, the test management team can adopt various approaches:
- Risk analyses detect mission-critical scenarios that must be checked at all costs, if an update, patch, or SAP transport is pending.
- Upgrade/change impact analyses, on the other hand, support testers in localizing and quantifying the expected technical impact of changes.
Alternative test tools
•Requires the test processes to have a certain level of maturity
•Is a long-term investment and does not generate a rapid return on investment
•Is software development and must be treated as such
•Should be structured in an evolutionary way
•Is primarily based on suitable methods, and then on the tools used
Regardless of the type of software test, test data and executable test scripts must always be strictly separated. The testers create the test scripts. In addition, the test cases should be driven by business cases and be modularized accordingly.
To ease cooperation between the professional test engineers and the business experts, a keyword-driven automation strategy is also recommended. Using this strategy, the automation activities on the GUI are reduced to just a few key words that are intelligible to all.