Testar - User contributions [en]

Main Page

2019-06-12T07:56:30Z

Tanja:

TESTAR

On this wiki we will describe how to install and use Testar. '''''If you want/need an account to contribute please send an e-mail to wiki@testar.org''' (Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.)''

__TOC__

== Automated testing at the Graphical User Interface Level == 

GUI Testing is a testing technique where one tests the System Under Test (SUT) solely through its Graphical User Interface (GUI). The only way to find errors is to thoroughly observe the status of the GUI throughout the test. This type of testing is usually still carried out manually, where a tester just follows a previously written test case and verifies whether the application responds to all inputs as expected.

On the one hand GUI testing is a relatively straightforward process, since one does not need to read or test the source code of the SUT. On the other hand it is quite laborious, time consuming and, well... boring...

Approaches for automation of GUI testing are for example Capture & Replay or Visual Testing. These approaches use test scripts to automate the steps of each test case. These type of tests, whether manual or automated through scripts, test the sunny day use cases and mostly follow the happy paths. But what about the less sunny test scenarios? Those scenarios executed by the rogue user?

== TESTAR ==
TESTAR is an open source tool for automated testing through GUI<ref>paper</ref>. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recognize abnormal SUT behaviour, such as crashing or freezing. Moreover, you can add application specific test oracles that are able to detect domain specific faults. TESTAR reports test sequences that lead to failure.

=== Virtual Environment ===

We have a [[Virtual environment]] at the UPV in Valencia.

=== Github open source community ===

=== How to get started (handson manual) ===
There exists a hands-on manual that will permit you to get started with automation of GUI testing using TESTAR. You can always get the latest version of this manual here:

[https://testar.org/download/ TESTAR download the hands-on manual]

In the manual it is explained how to get started with the latest version and a [[virtual machine]].

== FAQ ==

=== java.lang.RuntimeException: JDK required (running inside of JRE)===

If you get this error this means that your JAVA_HOME path does not point correctly to the installation path for the Java Development Kit.. To set your JAVA_HOME look for example here:

https://stackoverflow.com/questions/2619584/how-to-set-java-home-on-windows-7

=== Which platforms are supported? ===

The TESTAR binaries that are downloaded currently supports Windows. We have older versions that work with MacOS, Linux and Android.

=== What is required from the System Under Test (SUT)?===

Not much, just that the application respects the accesibility API of the underlying Operating System. For web applications you can use the WebDriver.

=== How is TESTAR licensed?===

TESTAR is distributed FREE of charge as an open source project under the BSD3 license

== Publications ==

=== From other people using TESTAR ===

* Mauro Pezzè, Paolo Rondena, and Daniele Zuddas. 2018. Automatic GUI testing of desktop applications: an empirical assessment of the state of the art. In Companion Proceedings for the ISSTA/ECOOP 2018 Workshops (ISSTA '18). ACM, New York, NY, USA, 54-62. DOI: https://doi.org/10.1145/3236454.3236489 (https://dl.acm.org/citation.cfm?id=3236489)

Main Page

2019-06-12T07:56:13Z

Tanja:

Main Page

2019-06-10T22:06:13Z

Tanja:

Virtual machine

2019-06-10T22:03:18Z

Tanja: Created page with "We recommend running TESTAR in a virtual machine. To run the virtual machine you will need to run virtualbox version 5.2.18 or later. If you do not have VirtualBox 5.2.18 on y..."

We recommend running TESTAR in a virtual machine. To run the virtual machine you will need to run virtualbox version 5.2.18 or later. If you do not have VirtualBox 5.2.18 on your machine you can download VirtualBox 5.2.18 here: https://download.virtualbox.org/virtualbox/5.2.18/

If you have a newer version (> 5.2.18) of VirtualBox installed, you might need to update the "VBox Guest Additions" on the virtual machine to the same version as your VirtualBox version. Please refer to the VirtualBox Manual on how to do this.

Minimal resource requirements for the VirtualBox Host:

* VirtualBox version $\geq$ 5.2.18
* Recent Dual core CPU or better
* 8 GB Memory
* 80 GB free diskspace

The hands-on OVA-image can be downloaded from the Testar website https://testar.org/images/
If you need any help, please send an email to \url{info@testar.org}.

Main Page

2019-06-10T22:00:03Z

Tanja:

TESTAR

On this wiki we will describe how to install and use Testar. '''''If you want/need an account to contribute please send an e-mail to wiki@testar.org''' (Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.)''

__TOC__

== Automated testing at the Graphical User Interface Level == 

GUI Testing is a testing technique where one tests the System Under Test (SUT) solely through its Graphical User Interface (GUI). The only way to find errors is to thoroughly observe the status of the GUI throughout the test. This type of testing is usually still carried out manually, where a tester just follows a previously written test case and verifies whether the application responds to all inputs as expected.

On the one hand GUI testing is a relatively straightforward process, since one does not need to read or test the source code of the SUT. On the other hand it is quite laborious, time consuming and, well... boring...

Approaches for automation of GUI testing are for example Capture & Replay or Visual Testing. These approaches use test scripts to automate the steps of each test case. These type of tests, whether manual or automated through scripts, test the sunny day use cases and mostly follow the happy paths. But what about the less sunny test scenarios? Those scenarios executed by the rogue user?

== TESTAR ==
TESTAR is an open source tool for automated testing through GUI. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recognize abnormal SUT behaviour, such as crashing or freezing. Moreover, you can add application specific test oracles that are able to detect domain specific faults. TESTAR reports test sequences that lead to failure.

=== Virtual Environment ===

We have a [[Virtual environment]] at the UPV in Valencia.

=== Github open source community ===

=== How to get started (handson manual) ===
There exists a hands-on manual that will permit you to get started with automation of GUI testing using TESTAR. You can always get the latest version of this manual here:

[https://testar.org/download/ TESTAR download the hands-on manual]

In the manual it is explained how to get started with the latest version and a [[virtual machine]].

== FAQ ==

=== java.lang.RuntimeException: JDK required (running inside of JRE)===

If you get this error this means that your JAVA_HOME path does not point correctly to the installation path for the Java Development Kit.. To set your JAVA_HOME look for example here:

https://stackoverflow.com/questions/2619584/how-to-set-java-home-on-windows-7

=== Which platforms are supported? ===

The TESTAR binaries that are downloaded currently supports Windows. We have older versions that work with MacOS, Linux and Android.

=== What is required from the System Under Test (SUT)?===

Not much, just that the application respects the accesibility API of the underlying Operating System. For web applications you can use the WebDriver.

=== How is TESTAR licensed?===

TESTAR is distributed FREE of charge as an open source project under the BSD3 license

Main Page

2019-06-10T21:51:11Z

Tanja:

TESTAR

On this wiki we will describe how to install and use Testar. '''''If you want/need an account to contribute please send an e-mail to wiki@testar.org''' (Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.)''

__TOC__

== Automated testing at the Graphical User Interface Level == 

GUI Testing is a testing technique where one tests the System Under Test (SUT) solely through its Graphical User Interface (GUI). The only way to find errors is to thoroughly observe the status of the GUI throughout the test. This type of testing is usually still carried out manually, where a tester just follows a previously written test case and verifies whether the application responds to all inputs as expected.

On the one hand GUI testing is a relatively straightforward process, since one does not need to read or test the source code of the SUT. On the other hand it is quite laborious, time consuming and, well... boring...

Approaches for automation of GUI testing are for example Capture & Replay or Visual Testing. These approaches use test scripts to automate the steps of each test case. These type of tests, whether manual or automated through scripts, test the sunny day use cases and mostly follow the happy paths. But what about the less sunny test scenarios? Those scenarios executed by the rogue user?

== TESTAR ==
TESTAR is an open source tool for automated testing through GUI. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recognize abnormal SUT behaviour, such as crashing or freezing. Moreover, you can add application specific test oracles that are able to detect domain specific faults. TESTAR reports test sequences that lead to failure.

=== Virtual Environment ===

We have a [[Virtual environment]] at the UPV in Valencia.

=== Github open source community ===

=== How to get started (handson manual) ===
There exists a hands-on manual that will permit you to take a look at automation of GUI testing using TESTAR. You can always get the latest version of this manual here:

[https://testar.org/download/ TESTAR download the hands-on manual]

== FAQ ==

=== java.lang.RuntimeException: JDK required (running inside of JRE)===

If you get this error this means that your JAVA_HOME path does not point correctly to the installation path for the Java Development Kit.. To set your JAVA_HOME look for example here:

https://stackoverflow.com/questions/2619584/how-to-set-java-home-on-windows-7

=== Which platforms are supported? ===

The TESTAR binaries that are downloaded currently supports Windows. We have older versions that work with MacOS, Linux and Android.

=== What is required from the System Under Test (SUT)?===

Not much, just that the application respects the accesibility API of the underlying Operating System. For web applications you can use the WebDriver.

=== How is TESTAR licensed?===

TESTAR is distributed FREE of charge as an open source project under the BSD3 license

Main Page

2019-06-10T21:50:47Z

Tanja:

TESTAR

On this wiki we will describe how to install and use Testar. '''''If you want/need an account to contribute please send an e-mail to wiki@testar.org''' (Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.)''

__TOC__

== Automated testing at the Graphical User Interface Level == 

GUI Testing is a testing technique where one tests the System Under Test (SUT) solely through its Graphical User Interface (GUI). The only way to find errors is to thoroughly observe the status of the GUI throughout the test. This type of testing is usually still carried out manually, where a tester just follows a previously written test case and verifies whether the application responds to all inputs as expected.

On the one hand GUI testing is a relatively straightforward process, since one does not need to read or test the source code of the SUT. On the other hand it is quite laborious, time consuming and, well... boring...

Approaches for automation of GUI testing are for example Capture & Replay or Visual Testing. These approaches use test scripts to automate the steps of each test case. These type of tests, whether manual or automated through scripts, test the sunny day use cases and mostly follow the happy paths. But what about the less sunny test scenarios? Those scenarios executed by the rogue user?

== TESTAR ==
TESTAR is an open source tool for automated testing through GUI. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recognize abnormal SUT behaviour, such as crashing or freezing. Moreover, you can add application specific test oracles that are able to detect domain specific faults. TESTAR reports test sequences that lead to failure.

=== Virtual Environment ===

We have a [[Virtual environment]] at the UPV in Valencia.

=== Github open source community ===

== How to get started ==
There exists a hands-on manual that will permit you to take a look at automation of GUI testing using TESTAR. You can always get the latest version of this manual here:

[https://testar.org/download/ TESTAR download the hands-on manual]

== FAQ ==

=== java.lang.RuntimeException: JDK required (running inside of JRE)===

If you get this error this means that your JAVA_HOME path does not point correctly to the installation path for the Java Development Kit.. To set your JAVA_HOME look for example here:

https://stackoverflow.com/questions/2619584/how-to-set-java-home-on-windows-7

=== Which platforms are supported? ===

The TESTAR binaries that are downloaded currently supports Windows. We have older versions that work with MacOS, Linux and Android.

=== What is required from the System Under Test (SUT)?===

Not much, just that the application respects the accesibility API of the underlying Operating System. For web applications you can use the WebDriver.

=== How is TESTAR licensed?===

TESTAR is distributed FREE of charge as an open source project under the BSD3 license

Main Page

2019-06-10T21:50:00Z

Tanja:

TESTAR

On this wiki we will describe how to install and use Testar. '''''If you want/need an account to contribute please send an e-mail to wiki@testar.org''' (Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.)''

__TOC__

== Automated testing at the Graphical User Interface Level == 

GUI Testing is a testing technique where one tests the System Under Test (SUT) solely through its Graphical User Interface (GUI). The only way to find errors is to thoroughly observe the status of the GUI throughout the test. This type of testing is usually still carried out manually, where a tester just follows a previously written test case and verifies whether the application responds to all inputs as expected.

On the one hand GUI testing is a relatively straightforward process, since one does not need to read or test the source code of the SUT. On the other hand it is quite laborious, time consuming and, well... boring...

Approaches for automation of GUI testing are for example Capture & Replay or Visual Testing. These approaches use test scripts to automate the steps of each test case. These type of tests, whether manual or automated through scripts, test the sunny day use cases and mostly follow the happy paths. But what about the less sunny test scenarios? Those scenarios executed by the rogue user?

== TESTAR ==
TESTAR is an open source tool for automated testing through GUI. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recognize abnormal SUT behaviour, such as crashing or freezing. Moreover, you can add application specific test oracles that are able to detect domain specific faults. TESTAR reports test sequences that lead to failure.

We have a [[Virtual environment]] at the UPV in Valencia.

== How to get started ==
There exists a hands-on manual that will permit you to take a look at automation of GUI testing using TESTAR. You can always get the latest version of this manual here:

[https://testar.org/download/ TESTAR download the hands-on manual]

== FAQ ==

=== java.lang.RuntimeException: JDK required (running inside of JRE)===

If you get this error this means that your JAVA_HOME path does not point correctly to the installation path for the Java Development Kit.. To set your JAVA_HOME look for example here:

https://stackoverflow.com/questions/2619584/how-to-set-java-home-on-windows-7

=== Which platforms are supported? ===

The TESTAR binaries that are downloaded currently supports Windows. We have older versions that work with MacOS, Linux and Android.

=== What is required from the System Under Test (SUT)?===

Not much, just that the application respects the accesibility API of the underlying Operating System. For web applications you can use the WebDriver.

=== How is TESTAR licensed?===

TESTAR is distributed FREE of charge as an open source project under the BSD3 license

Main Page

2019-06-10T21:49:39Z

Tanja:

TESTAR

On this wiki we will describe how to install and use Testar. '''''If you want/need an account to contribute please send an e-mail to wiki@testar.org''' (Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.)''

__TOC__

== Automated testing at the Graphical User Interface Level == 

GUI Testing is a testing technique where one tests the System Under Test (SUT) solely through its Graphical User Interface (GUI). The only way to find errors is to thoroughly observe the status of the GUI throughout the test. This type of testing is usually still carried out manually, where a tester just follows a previously written test case and verifies whether the application responds to all inputs as expected.

On the one hand GUI testing is a relatively straightforward process, since one does not need to read or test the source code of the SUT. On the other hand it is quite laborious, time consuming and, well... boring...

Approaches for automation of GUI testing are for example Capture & Replay or Visual Testing. These approaches use test scripts to automate the steps of each test case. These type of tests, whether manual or automated through scripts, test the sunny day use cases and mostly follow the happy paths. But what about the less sunny test scenarios? Those scenarios executed by the rogue user?

== TESTAR ==
TESTAR is an open source tool for automated testing through GUI. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recognize abnormal SUT behaviour, such as crashing or freezing. Moreover, you can add application specific test oracles that are able to detect domain specific faults. TESTAR reports test sequences that lead to failure.

We have a [[Virtual environment]] at the UPV in Valencia-

== How to get started ==
There exists a hands-on manual that will permit you to take a look at automation of GUI testing using TESTAR. You can always get the latest version of this manual here:

[https://testar.org/download/ TESTAR download the hands-on manual]

== FAQ ==

=== java.lang.RuntimeException: JDK required (running inside of JRE)===

If you get this error this means that your JAVA_HOME path does not point correctly to the installation path for the Java Development Kit.. To set your JAVA_HOME look for example here:

https://stackoverflow.com/questions/2619584/how-to-set-java-home-on-windows-7

=== Which platforms are supported? ===

The TESTAR binaries that are downloaded currently supports Windows. We have older versions that work with MacOS, Linux and Android.

=== What is required from the System Under Test (SUT)?===

Not much, just that the application respects the accesibility API of the underlying Operating System. For web applications you can use the WebDriver.

=== How is TESTAR licensed?===

TESTAR is distributed FREE of charge as an open source project under the BSD3 license

Main Page

2019-06-10T21:48:53Z

Tanja:

Main Page

2019-06-10T21:48:29Z

Tanja:

Main Page

2019-06-10T21:47:16Z

Tanja:

Main Page

2019-06-10T21:46:11Z

Tanja:

Main Page

2019-06-10T21:45:12Z

Tanja:

TESTAR

2019-06-10T21:43:20Z

Tanja: Created page with "TESTAR is an open source tool for automated testing through GUI. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recog..."

TESTAR is an open source tool for automated testing through GUI. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recognize abnormal SUT behaviour, such as crashing or freezing. Moreover, you can add application specific test oracles that are able to detect domain specific faults. TESTAR reports test sequences that lead to failure.

Main Page

2019-06-10T21:42:52Z

Tanja:

Handson

2019-06-10T21:42:07Z

Tanja:

There exists a hands-on manual that will permit you to take a look at automation of GUI testing using TESTAR. You can always get the latest version of this manual here:

[https://testar.org/download/ TESTAR download the hands-on manual]

Handson

2019-06-10T21:39:28Z

Tanja: Created page with "There exists a hands-on manual that will permit you to take a look at automation of GUI testing using TESTAR. TESTAR is a test tool that automatically tests the less sunny use..."

There exists a hands-on manual that will permit you to take a look at automation of GUI testing using TESTAR. TESTAR is a test tool that automatically tests the less sunny use cases through random and monkey tests. It hence complements the other approaches:

TESTAR is an open source tool for automated testing through GUI. It automatically interacts with the SUT by clicking and typing on the controls of the GUI. It is able to recognize abnormal SUT behaviour, such as crashing or freezing. Moreover, you can add application specific test oracles that are able to detect domain specific faults. TESTAR reports test sequences that lead to failure.

Automated testing at the Graphical User Interface Level

2019-06-10T21:38:06Z

Tanja: Created page with "GUI Testing is a testing technique where one tests the System Under Test (SUT) solely through its Graphical User Interface (GUI). The only way to find errors is to thoroughly..."

GUI Testing is a testing technique where one tests the System Under Test (SUT) solely through its Graphical User Interface (GUI).
The only way to find errors is to thoroughly observe the status
of the GUI throughout the test. This type of testing is usually still carried out manually, where a tester just follows a previously written ''test case'' and verifies whether the
application responds to all inputs as expected.

On the one hand GUI testing is a relatively straightforward process, since one does not need to read or test the source code
of the SUT. On the other hand it is quite laborious, time consuming and, well... boring...

Approaches for automation of GUI testing are for example Capture & Replay or Visual Testing. These approaches use test scripts to automate the steps of each test case. These type of tests, whether manual or automated through scripts, test the sunny day use cases and mostly follow the happy paths. But what about the less sunny test scenarios? Those scenarios executed by the rogue user?

Main Page

2019-06-10T21:37:23Z

Tanja:

Main Page

2019-06-10T21:37:02Z

Tanja:

Main Page

2019-06-10T21:36:33Z

Tanja:

Main Page

2019-06-10T21:34:30Z

Tanja:

Main Page

2019-06-10T21:31:42Z

Tanja:

On this wiki we will describe how to install and use Testar. '''''If you want/need an account to contribute please send an e-mail to wiki@testar.org''' (Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.)''

<br />

* We have a [[Virtual environment]] at the UPV