Installation

  • Getting started

Installation

suittest has been developed to be easy to install and try, (but depending on the technology under testing, more configuration may be necessary)

  • The first step is to log onto suittest and click in Download Runner.

The Runner is the executable that allows you to perform various tasks in web applications and if desired, also mobile applications. The Runner allows you to use the Debug mode, the Record & Play (for example for the test creation) and execute or schedule tests.

  • Once the download is complete, simply extract the ZIP file into any folder in the machine
  • Execute the suittest.exe (you can create a shortcut if you want)
  • After opening, the Runner will update for the first time (other updates will happen automatically). After the installation, the default technologies (web, app, mobile, database, webservices and others) will be available. Note: For Web Service testing using SoapUI, it is required to install SoapUI
  • You only have to fill the fields in the runner executable to do the conexion to the server:
    • Server is the suittest link
    • Username is the user to be logged
    • Password for the user password
  • Click on Authenticate. If everything is correct, the Project Combobox will now have options, select the desired project and the Runner will be connected:

Next steps: Now you can continue the following steps


Recomendations

For Web and Desktop testing, some configurations are recommended:

  • The Desktop screen text size must be 100%
  • Browser zoom (both app under testing and suittest web app must be 100%)
  • IE only:
    • Internet Explorer Security zone setting must have Enabled protected mode equal for all 4 (enabled or disabled)
    • Internet Explorer must have tabs open a new tab by default

Notes:

  • For Web Service testing using SoapUI, it is required to install SoapUI
  • For mobile configuration you only need to follow the mobile instructions included here for Android and iOS and in suittest application manual

Resolved issues:

  • A common issue is OneDrive (or other Cloud saving applications that replace system folders) can cause conflicts with the Runner installing/updating/executing tests. This issue is caused by these Cloud Platforms "locking" necessary files. To fix this issue, make sure that the Cloud Platforms either don't have access to the Documents and Downloads folder, or create an exception for the Folder where all the Logs/Video Evidences are stored (by default it's in the Documents/TestingTool folder)
  • For OneDrive in particular another issue may arise:
    • OneDrive can replace the system's default Documents folder with a Documents fodler created by OneDrive (from C:\Users\USER\Documents to C:\Users\USER\OneDrive\Documents)
    • If this happens, it may be needed to restore the Documents folder to it's default state