Test automation helps us automate some repetitive but necessary tasks in a formalized testing lifecycle, or add additional testing to save extra time spent on regression testing. At Magnic Digital, we use tools like Selenium, Jenkins, Rubidium, Cucumber, Capybara, Monkey Talk, HP QTP and HP UFT to control the execution of tests and the comparison of actual outcomes to the expected ones.
There are many approaches to test automation; however below are the general approaches used widely:

• Graphical user interface testing: A testing framework that generates user interface events such as keystrokes and mouse clicks, and observes the changes that result in the user interface, to validate that the observable behavior of the program is correct.
• API driven testing: A testing framework that uses a programming interface to the application to validate the behavior under test. Typically, API driven testing bypasses application user interface altogether. It can also be testing public (usually) interfaces to classes, modules or libraries are tested with a variety of input arguments to validate that the results that are returned are correct. Goal is not to reduce test resources or testing cycle time, it is to reduce the risk and cost of software failure by increasing the test coverage.