Misplaced Pages

Test automation

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

This is an old revision of this page, as edited by Thv (talk | contribs) at 07:22, 18 April 2005 (See also: Model-based testing). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 07:22, 18 April 2005 by Thv (talk | contribs) (See also: Model-based testing)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

Over the past few years, tools that help programmers quickly create applications with graphical user interfaces have dramatically improved programmer productivity. This has increased the pressure on testers, who are often perceived as bottlenecks to the delivery of software products. Testers are being asked to test more and more code in less and less time. Test automation is one way to do this, as manual testing is time consuming. As and when different versions of a software are released, the new features will have to be tested manually time and again. But, now there are tools available that help the testers in the automation of the GUI which reduce the test time as well as the cost, other test automation tools support execution of performance tests.

Many test automation tools provide record and playback features that allow users to record interactively user actions and replay it back any number of times, comparing actual results to those expected.

A growing trend in software development is to use testing frameworks such as the JUnit or NUnit frameworks which allow the code to conduct unit tests to determine whether various sections of the code are acting as expected in various circumstances. Test cases describe tests that need to be run on the program to verify that the program runs as expected. In a properly tested program, there is at least test in the software code designed to satisfy a unit test requirement.

See also

Stub icon

This computing article is a stub. You can help Misplaced Pages by expanding it.

Categories: