Legacy system

1. A method, comprising:

encapsulating, by a controller, a plurality of recorded user interface (UI) automation scripts of an existing legacy system with an application programming interface (API) wrapper associated with a mobile application;

in response to a call from the mobile application, utilizing, by the controller, a selected one of the plurality of recorded UI automation scripts encapsulated in the API wrapper to execute at least one action in the legacy system, wherein the selected UI automation script replays functions of the legacy system based on at least one API of the legacy system, and wherein utilizing comprises utilizing the selected UI automation script to replay the functions of the legacy system based on the at least one API of the legacy system;

returning, by the controller, results from the at least one action in the legacy system to the mobile application;

determining, by the controller, that a failure exists in at least one of the plurality of recorded UI automation scripts; and

correcting, by the controller, the at least one of the plurality of recorded UI automation scripts in which a failure is determined to exist without changing any code in the mobile application.

2. The method of claim 1 , wherein utilizing comprises inserting data into the legacy system and retrieving data from the legacy system with the selected UI automation script by using a parameter set by the selected UI automation script.

3. The method of claim 1 , further comprising recording the plurality of UI automation scripts of the legacy system with a record-replay engine at a mobile integrated development environment (IDE).

4. The method of claim 1 , wherein the selected UI automation script is to execute a plurality of steps related to the at least one action in the legacy system; and utilizing comprises utilizing the selected UI automation script to execute the plurality of steps related to the at least one action in the legacy system.

5. The method of claim 1 , wherein the selected UI automation script is to perform functions not enabled by the legacy system.

6. A system comprising:

a mobile integrated development environment (IDE) in communication with at least one legacy system;

a record-replay engine in communication with the IDE; and

a computing device having a control unit to:

create at least one user interface (UI) automation script of the legacy system by using the record-replay engine,

wrap the at least one UI automation script with an application programming interface (API) wrapper of the mobile application,

execute at least one action in the legacy system by calling the at least one UI automation script in the API wrapper, wherein the at least one UI automation script replays functions of the legacy system based on at least one API of the legacy system, and utilizing the at least one UI automation script to replay the functions of the legacy system based on the at least one API of the legacy system,

continuously determine whether a failure exists in the least one UI automation script,

generate data based on at the least one action in the legacy system;

determine that a failure exists in the at least one UI automation script; and

correct the at least one UI automation script in which a failure is determined to exist without changing any code in the mobile application.

7. The system of claim 6 , wherein the control unit is to insert data into the legacy system and is to retrieve data from the legacy system with the at least one UI automation script by using a parameter set by the UI automation script.

8. The system of claim 6 , wherein the at least one UI automation script is to execute a plurality of steps related to the at least one action in the legacy system.

9. A non-transitory machine-readable storage medium encoded with instructions executable by a processor, the machine-readable storage medium comprising instructions to:

encapsulate a plurality of recorded user interface (UI) automation scripts of an existing legacy system with an application programming interface (API) wrapper for a mobile application, where the plurality of UI automation scripts replay functions of the legacy system based on at least one API of the legacy system;

access the legacy system with the mobile application by calling the API wrapper;

utilize a selected one of the plurality of recorded UI automation scripts in the API wrapper to execute an action in the legacy system, wherein the selected UI automation script replays functions of the legacy system based on at least one API of the legacy system, and to utilize the selected one of the plurality of recorded UI automation scripts, utilize the selected UI automation script to replay the functions of the legacy system based on the at least one API of the legacy system;

generate data displayed at the mobile application based on at the least one action in the legacy system;

determine that a failure exists in at least one of the plurality of recorded UI automation scripts; and

correct the at least one of the plurality of recorded UI automation scripts in which a failure is determined to exist without changing any code in the mobile application.

10. The non-transitory machine-readable storage medium of claim 9 , further comprising instructions to insert data into the legacy system and retrieve data from the legacy system with the selected UI automation script by using a parameter set by the UI automation script.