How to set TESTAR with different SUT - Revision history

Fernando: Add webdriver protocol

2019-09-15T17:59:51Z

Add webdriver protocol

← Older revision		Revision as of 17:59, 15 September 2019
Line 6:		Line 6:
	====COMMAND_LINE====		====COMMAND_LINE====

	* Prerequisites (SUT is not yet running)		*Prerequisites (SUT is not yet running)

	This configuration mode consists of indicate the location of an executable file, execute them according to the type of the file (application.exe, java -jar application.jar, etc...). Then TESTAR, after launching the SUT, will connect with the process of the current application to test.		This configuration mode consists of indicate the location of an executable file, execute them according to the type of the file (application.exe, java -jar application.jar, etc...). Then TESTAR, after launching the SUT, will connect with the process of the current application to test.
Line 12:		Line 12:
	Example:		Example:

	# Selecting "C:\\Windows\\System32\\notepad.exe" like SUT, TESTAR will execute this file and connect with the main process.		#Selecting "C:\\Windows\\System32\\notepad.exe" like SUT, TESTAR will execute this file and connect with the main process.

	<br />		<br />

	* Additional: Finish TESTAR will close the SUT		*Additional: Finish TESTAR will close the SUT

	<br />		<br />
	====SUT_WINDOWS_TITLE====		====SUT_WINDOWS_TITLE====

	* Prerequisites (SUT is running)		*Prerequisites (SUT is running)
	* The GUI windows of the SUT must be in the foreground; otherwise, TESTAR will not be able to find it.		*The GUI windows of the SUT must be in the foreground; otherwise, TESTAR will not be able to find it.

	This configuration mode consists of indicating a String that matches with the Title of the running GUI window that we desire to test.		This configuration mode consists of indicating a String that matches with the Title of the running GUI window that we desire to test.
Line 32:		Line 32:
	Examples:		Examples:

	# Windows Notepad application is running with a non saved document. Into the top of the GUI windows the Title contains "Untitled", so we can use this String as a Title match.		#Windows Notepad application is running with a non saved document. Into the top of the GUI windows the Title contains "Untitled", so we can use this String as a Title match.
	# We opened a document called "Shopping list", the we can use "Shopping" as a Title match.		#We opened a document called "Shopping list", the we can use "Shopping" as a Title match.

	<br />		<br />

	* Additional: Finish TESTAR will NOT close the SUT		*Additional: Finish TESTAR will NOT close the SUT

	<br />		<br />
	====SUT_PROCESS_NAME====		====SUT_PROCESS_NAME====

	* Prerequisites (SUT is running)		*Prerequisites (SUT is running)

	This configuration mode consists of indicating a String that matches with the process name of the desired SUT to test.		This configuration mode consists of indicating a String that matches with the process name of the desired SUT to test.
Line 52:		Line 52:
	Example:		Example:

	We have Windows Notepad (notepad.exe) and Notepad++ (notepad++.exe) applications running in our environment., and we configure TESTAR with a SUT_PROCESS_NAME connection and we indicate the process name as "notepad".		# We have Windows Notepad (notepad.exe) and Notepad++ (notepad++.exe) applications running in our environment., and we configure TESTAR with a SUT_PROCESS_NAME connection and we indicate the process name as "notepad".

	Both applications match with the String "notepad", so TESTAR will return the first process that matches as SUT.		Both applications match with the String "notepad", so TESTAR will return the first process that matches as SUT.
	<br />		<br />

	* Additional: Finish TESTAR will NOT close the SUT		*Additional: Finish TESTAR will NOT close the SUT

	<br />		<br />
Line 64:		Line 64:

	====WEB_DRIVER====		====WEB_DRIVER====

			* Download Selenium Webdriver (https://chromedriver.chromium.org/downloads)
			* Prerequisites (SUT is not yet running)

			This configuration mode consists of indicating the location of the downloaded Selenium Webdriver and the URL of the desired web page to test. In the Webdriver protocol (use the "Edit protocol" button) we will need to customize the test domain of TESTAR executions, or disable this feature.

			Chrome browser will open with the selected web page and the webdriver will begin to act as a GUI API that allows TESTAR to detect all widgets of the DOM and perform actions on these widgets.


			Example:

			# We select the location of the Webdriver "C:\\Windows\\chromedriver.exe" and the web page that will act as SUT "https:\\www.ou.nl". TESTAR will open the Chrome browser and execute the selected mode.

	<br />		<br />

			* Additional: Finish TESTAR will close the SUT


			This protocol has some interesting advanced configuration options that the user must know to improve the use of TESTAR. In this link we show more advanced details about this configuration: [[How to set TESTAR with Webdriver protocol]]<br />

	==How is running the SUT?==		==How is running the SUT?==
	<br />		<br />

	== Special/Particular applications ==		==Special/Particular applications==

	===== Windows 10 applications (Example Windows 10 Calculator) =====		=====Windows 10 applications (Example Windows 10 Calculator)=====

	===== Java applications launched under .exe file =====		=====Java applications launched under .exe file=====

	===== Multi processes applications =====		=====Multi processes applications=====

Fernando: Add information into How to set TESTAR and SUT

2019-09-13T12:10:51Z

Add information into How to set TESTAR and SUT

@@ Line 1: / Line 1: @@
 Here we are going to describe the different TESTAR options to connect with the desired application to test, also called System Under Test (SUT). Moreover, to choose the best option, we need to understand how the SUT is running into the environment.
-== TESTAR main version ==
+==TESTAR main version==
 TESTAR main version offers three different options to connect with the SUT.
-==== COMMAND_LINE ====
+====COMMAND_LINE====
 <br />
-==== SUT_WINDOWS_TITLE ====
+* Additional: Finish TESTAR will close the SUT
 <br />
 <br />
-== TESTAR WebDriver version ==
+* Additional: Finish TESTAR will NOT close the SUT
 TESTAR WebDriver offers an additional option to connect to the desired SUT using the Selenium webdrivers.
-==== WEB_DRIVER ====
+====WEB_DRIVER====
 <br />
-== How is running the SUT? ==
+==How is running the SUT?==
 <br />

Fernando: Create Page: "How to set TESTAR with different SUT"

2019-08-27T10:32:28Z

Create Page: "How to set TESTAR with different SUT"

New page

Here we are going to describe the different TESTAR options to connect with the desired application to test, also called System Under Test (SUT). Moreover, to choose the best option, we need to understand how the SUT is running into the environment.

== TESTAR main version ==
TESTAR main version offers three different options to connect with the SUT.

==== COMMAND_LINE ====
 

==== SUT_WINDOWS_TITLE ====
 

==== SUT_PROCESS_NAME ====
 

== TESTAR WebDriver version ==
TESTAR WebDriver offers an additional option to connect to the desired SUT using the Selenium webdrivers.

==== WEB_DRIVER ====
 

== How is running the SUT? ==