Test automation: Difference between revisions

Revision as of 14:33, 23 March 2025

Revision as of 14:34, 23 March 2025

Line 29:

{{main article|Graphical user interface testing}}

<ref>{{Cite web |last=Thakkar |first=Mit |date=April 29, 2024 |title=Test Automation Strategy: Key Practices for Successful Implementation |url=https://www.kiwiqa.com.au/test-automation-strategy/ |url-status=live |archive-date= |website=https://www.kiwiqa.com.au/}}</ref>Many test automation tools provide record and playback features that allow users to interactively record user actions and replay them back any number of times, comparing actual results to those expected. The advantage of this approach is that it requires little or no [[software development]]. <ref></ref>InThis theapproach firstcan be applied to any application that has a [[graphical user interface]]. stepHowever, youreliance shouldon selectthese features poses major reliability and maintainability problems. Relabelling a button or moving it to another part of the rightwindow automationmay testingrequire toolthe test to improvebe yourre-recorded. developmentRecord processand playback also often adds irrelevant activities or incorrectly records some activities.{{Citation needed|date=March 2013}}

Secondly, you have to determine which type of test execution shall go on automation testing. Mostly, regression test cases are best for automation testing as they are complex programs, and manual execution takes more time.

Thirdly, make sure your testing is well organized and that all the resources are present in the test.

Then, you have to test on a behavior-driven framework to ensure your test is in accordance with the customer’s perspective.

After that, define the scope of the automation with your team. Also, discuss which part of the programs needs automation and test data.

To check the test process is reliable and accurate, you should perform test script development.

Then, execute the test in the chosen platform or tool.This approach can be applied to any application that has a [[graphical user interface]]. However, reliance on these features poses major reliability and maintainability problems. Relabelling a button or moving it to another part of the window may require the test to be re-recorded. Record and playback also often adds irrelevant activities or incorrectly records some activities.{{Citation needed|date=March 2013}}

A variation on this type of tool is for testing of web sites. Here, the "interface" is the web page. However, such a framework utilizes entirely different techniques because it is rendering [[HTML]] and listening to [[DOM Events]] instead of operating system events. [[Headless browser]]s or solutions based on [[Selenium (Software)#Selenium WebDriver|Selenium Web Driver]] are normally used for this purpose.<ref>Headless Testing with Browsers; https://docs.travis-ci.com/user/gui-and-headless-browsers/</ref><ref name="Headless Testing with Browsers">Headless Testing with PhantomJS;http://phantomjs.org/headless-testing.html</ref><ref>Automated User Interface Testing; https://www.devbridge.com/articles/automated-user-interface-testing/</ref>

Line 42 ⟶ 36:

Another variation is script-less test automation that does not use record and playback, but instead builds a model{{clarify|date=June 2016}} of the application and then enables the tester to create test cases by simply inserting test parameters and conditions, which requires no scripting skills.

==Methodologies==