Test automation: Difference between revisions

Revision as of 11:52, 8 August 2025

Revision as of 12:00, 8 August 2025

Line 41:

Testing tools can help automate tasks such as product installation, test data creation, GUI interaction, problem detection (consider parsing or polling agents equipped with [[test oracle]]s), defect logging, etc., without necessarily automating tests in an end-to-end fashion.

Considerations when developing automated tests include:

One must keep satisfying popular requirements when thinking of test automation:

* [[Computing platform |Platform]] and [[Operatingoperating system|OS]] independence

* [[Data -driven capability (Input Data, Output Data, [[Metadatatesting]])

* Customization Reporting (DB [[Data Basedatabase]] Access, [[Crystal Reports]])

* EasyEase of [[debugging and logging]]

* [[Logging (computing)|Logging]]

* [[Version control]] friendly – minimal binary files

* [[Version control]]

* Extensible & Customization (Open [[API]]s to be able to integrate with other tools)

* Extension and customization; [[API]]s for integrating with other tools

* Common Driver (For example, in the Java development ecosystem, that means [[Apache Ant|Ant]] or [[Apache Maven|Maven]] and the popular [[Integrated Development Environment|IDEs]]). This enables tests to integrate with the developers' [[workflows]].

* Integration with developer tools; for example, using [[Apache Ant |Ant]] or [[Apache Maven |Maven]] for [[Java]] development

* Support unattendedUnattended test runs for integration with build processes and batch runs. [[Continuous integration]] servers require this.

* Email Notificationsnotifications; likei.e. [[bounce message]]s

* Support distributed execution environment (distributed [[Testbed|test bed]])

* Distributed applicationtest support (distributed [[System Under Test|SUT]])execution

==Roles==