Differences

This shows you the differences between two versions of the page.

--- plugins [2020/07/16 19:52] – [TestOptimal Plugins] admin
+++ plugins [2024/01/02 22:41] (current) – removed admin
@@ Line 1: / Line 1: @@
-===== TestOptimal Plugins =====
-//TestOptimal// uses plugin architecture to provide the flexibility for integrating with external test automation framework and tools.
-Note that most of the plugins are built on or integrated with external drivers. //TestOptimal// only supports the integration with these external drivers and not the external drivers.
-You may also [[tutorial:plugins | develop your own plugin]] to extend functionality of //TestOptimal// or integrate with your proprietary framework/system.
-Below are the plugins available:
-  * [[#Agent Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/AgentPlugin.html|javadoc]])
-  * [[#Appium Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/AppiumPlugin.html|javadoc]])
-  * [[#MQTT Plugin ]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/MqttPlugin.html|javadoc]])
-  * [[#Random Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/RandPlugin.html|javadoc]])
-  * [[#REST Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/RestPlugin.html|javadoc]])
-  * [[#Selenium Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/SeleniumPlugin.html|javadoc]])
-  * [[#SeqOut Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/SeqOutPlugin.html|javadoc]])
-  * [[#Sikuli Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/SikuliXPlugin.html|javadoc]])
-  * [[#WebDriver Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/WebDriverPlugin.html|javadoc]])
-  * [[#XUIA Plugin]] ([[https://testoptimal.com/v6/apidocs/com/testoptimal/plugin/XUIAPlugin.html|javadoc]])
-Plugin javadoc is available [[https://testoptimal.com/v6/apidocs | HERE]].
-//Plugins// must be activated for the model before they can be used through [[ide_script | Script Editor]].
-----
-==== Agent Plugin ====
-//Agent Plugin// enables integration with external automation tools and processes through http protocol.
-Example remote agent:
-  * [[remoteagentautoit | AutoIT]]
-----
-==== Appium Plugin ====
-//Appium Plugin// is used to test web apps and native apps on mobile devices.
-=== Pre-Requisite ===
-//Appium Plugin// requires [[http://appium.io|Appium]] be installed on the computer which the mobile devices will be attached or mobile simulators will be installed.
-Additionally, you will need [[https://developer.android.com/studio/index.html | Android Studio/SDK]] to test //Android// devices and [[https://developer.apple.com/downloads/index.action | Apple Xcode]] to test //IOS// devices.
-----
-==== MQTT Plugin ====
-//MQTT Plugin// enables testing of [[https://mqtt.org/ | MQTT]]-based IoT devices.
-----
-==== REST Plugin ====
-//REST Plugin// enables testing of REST and WebSvc using [[http://rest-assured.io/| RestAssured]].
-----
-==== Random Plugin ====
-//RAND Plugin// provides a set of pattern-based random data generation.  For example, you can generate random street address, zip code or random number from a random distribution.
-----
-==== Selenium Plugin ====
-//Selenium Plugin// uses [[http://seleniumhq.org/|Selenium]] to perform test automation on your web application with various browsers. The simulated browser (HTMLUNIT) offers much higher performance and more suited for running load testing when you need to simulate hundreds or thousands of users running models simultaneously.
-=== Element Locator ===
-Need help with element locator?  Check out these links:
-  * [[https://www.simple-talk.com/dotnet/.net-framework/xpath,-css,-dom-and-selenium-the-rosetta-stone/ | Michael Sorens' post on Selenium locator]]:
-  * [[http://www.simple-talk.com/content/file.ashx?file=4937 | Xpath * CSS * DOM * Selenium: Rosetta Stone and Cookbook, page 1]]
-  * [[http://www.simple-talk.com/content/file.ashx?file=4938 | Xpath * CSS * DOM * Selenium: Rosetta Stone and Cookbook, page 2]]
-  * [[http://www.techbeamers.com/use-locators-selenium/ | 8 Ways To Use Locators For Selenium Testing]]
-Tools to help find the web element locator:
-  * Firefox add-on [[https://addons.mozilla.org/en-US/firefox/addon/element-locator-for-webdriv/ | WebDriver Element Locator]]
-  * [[http://www.softwaretestinghelp.com/locate-elements-in-chrome-ie-selenium-tutorial-7/ | How to locate elements in Chrome and IE]]
-----
-==== SeqOut Plugin ====
-//SeqOut Plugin// generates the test sequence from your model script to an HTML webpage, Excel document or text/xml/json files for external automation tools.
-----
-====SikuliUIA Plugin ====
-//Sikuli Plugin// provides a set of [[http://testoptimal.com/javaDoc/reference/com/webmbt/plugin/SikuliPlugin.html| mscript functions]] for interacting with any type of //UI Applications//. Due to the nature of using image to identify the UI control, the performance will be a little bit slower.
-[[http://testoptimal.com/javaDoc/reference/com/webmbt/plugin/SikuliPlugin.html| MScript Functions]]
-=== UI Images ====
-//Sikuli// uses images to identify UI controls.  The images must be //png//.
-Image files must be stored in ///uimap/// subfolder within the model folder.
-----
-==== WebDriver Plugin =====
-//WebDriver Plugin// enables testing with products/services implementing [[https://www.w3.org/TR/webdriver1/| WebDriver wire protocol]], more info at [[https://www.selenium.dev/documentation/en/webdriver/ | WebDriver Documentation]].
-Below is a few examples of such products/services:
-  * [[https://github.com/microsoft/WinAppDriver|WinAppDriver]]
-  * [[https://github.com/2gis/Winium|Winium]]
-  * [[https://saucelabs.com/ | SauceLabs]]
-  * [[https://www.browserstack.com/automate?utm_campaign=open-source-sponsor&utm_source=seleniumorg&utm_medium=referral | BrowserStack]]
-----
-====XUIA Plugin ====
-//XUIA Plugin// provides a set of [[http://testoptimal.com/javaDoc/reference/com/webmbt/plugin/XUIAPlugin.html| mscript functions]] for automation using keyboard and mouse.
-The automation is accomplished by sending the real keyboard event and mouse movement to AUT. Due to the nature of this type of automation, you must ensure AUT you are automating has the focus just like as if you are testing manually.