|
Architecture
|
|
As illustrated in the diagram below, the TestFactory Test Suite process is straightforward. TestFactory is installed directly into SAP via a traditional transport methodology. Thus, business users simply record the processes that model the usage scenarios in production using the SAP interface that they are familiar with. Data dependencies between transactions are automatically mapped out.
Using standard SAP GUI screens and portal pages, the users then organize tests into hierarchical lists of business processes under project folders to model real-life usage.
They can quickly validate the business process by simply re-running the test model and viewing the screens. As necessary, they can adjust the data input by a simple click of a button to specify whether the system should automatically generate unique, random, time related data, or to select from an existing SAP table. All of this with no scripting, no programming, no spreadsheets!
Now we are ready to run the real world SAP functional, security or performance test. Using a typical "day in the life" profile, all of the necessary business process are managed and directed by the TestFactory Appliance to the necessary agents to simulate real user load via SAPGui or Web browser sessions.
Detailed test results are captured and stored, including end user response time, dialog steps, infrastructure metrics and so forth. Historical data allows you to compare different runs to ensure that any tuning efforts are having a positive impact to the business.
End user administration including user-ids and passwords are automatically managed. Unlike traditional solutions, TestFactory Performance Test can even simulate external interfaces from third-party applications via RFC, Bapi, HTTP or file transfer using a similar approach. Now let's take a look at how TestFactory handles a very common and important scenario involving EDI Trading partners.
EDI Emulation
EDI trading partner simulation is also possible by implementing customer EDI-to-IDOC maps in the TestFactory appliance. The appliance acts as an ALE server to process outbound EDI messages and create inbound EDI messages.
An example of a typical use case might involve purchasing a product via an EDI trading partner network. The TestFactory appliance can be configured to generate turn-around documents like advance shipping notices and invoices. This allows business processes to be tested without involving a third-party trading partner. This is a valuable testing tactic to ensure that end-to-end business processes continue to function as SAP changes are made internally that should have no effect on existing implementations of EDI transactions.
EDI emulation does not replace the need to unit-test changes in EDI maps that must be sent to trading partners for verification. However, once implemented, EDI transactions do not tend to change very often. TestFactory EDI emulation allows an SAP technical organization to be self-sufficient in testing end-to-end business processes.
This same concept applies to any interface between a third-party software system and SAP. TestFactory can emulate the connected software system in order to allow an entire business process to be verified without actually contacting the external system.
|
