T-Plan Robot Frequently Asked Questions
We schedule a point release every quarter, with a major release once a year. A breakdown of releases for example can be found in our T-Plan Robot Enterprise Versions document.
We also have an OTA (over the air) update mechanism, where customers can get automatic upgrades & updates to bug fixes etc. When bugs are reported we are not beaten by anyone in our speed to get these turned around. Where applicable these fixes can be released as a ‘point.point’ release; to a specific customer, or the customer base as a whole.
Java 6 (formerly 1.6) or higher. If you want to take advantage of Java test scripts, you have to use the Java Development Kit 6 (JDK 6) instead of Java Runtime Environment 6 (JRE 6). The difference is that JDK contains compiler needed for runtime compilation of Java code. If you use just a JRE, the tool will run but it won’t allow you to compile and execute Java source code (.java files). This limitation doesn’t apply to already compiled Java test scripts (.class files). Java requirements are documented in the Release Notes document.
T-Plan Robot Enterprise uses two types of license:
Development – design, develop and debug projects using the Robot Enterprise application.
Execution – execution only licenses can be pooled to allow multiple concurrent executions across different projects and System Under Test’s (SUT’s).
All of T-Plan Robot licenses can be used on any platform to automate any environment. Windows, Mac, Desktop, Web, Mobile, iOS, Android – mix and match as you please.
Trials are offered with file based licenses which are sent via email. They offer provision for both the development and execution of test scripts through the T-Plan Robot UI and/or CLI. These are installed locally, along with Robot, or on a centrally accessible shared network directory.
The trial licenses are fully functional and restricted only by time. When the trial period expires, whilst you do not lose any work that you have done, you will be unable to run any aspect of T-Plan Robot. When you purchase the product the product will resume and you can continue your work.
No. You must purchase at least one Development license in order to design and develop your test projects, prior to being able to execute them.
During a valid support and maintenance contract you have full access to all product updates. Beta and minor point releases, through to major feature releases are all included.
If you have any problems or questions, or simply want some advice, you can communicate with our support team through phone, email, web chat or our support forums.
The Development License is not named to an individual, and not tied to a particular computer, i.e. the license is floating, not node locked.
For an example purchase of 5 Development Licenses, this only allows 5 users to use T-Plan Robot Enterprise at any given time, even if there are 10 computers that have T-Plan Robot Enterprise installed on them.
In a multi user scenario the 5 development licenses are used by each user in turn, when they become available on the network. E.g. All other users will have to wait their turn on the network to use the 5 licenses. I.e. Only 5 license can be used at any one time.
Similarly a purchase of 5 Execution Licenses, only allows 5 connections to the System Under Test (SUT) at any one time.
Many existing features and improvements were actually suggested by active users who provided feedback. The T-Plan Robot community for us means the network of users who actively use the tool, and give us feedback. Whether it is a bug report, feature suggestion or recommendation on the web (email@example.com, contact details), our own forums, in public QA forums (such as SQAForums.com), or our forums at SourceForge, we aim to address your wants and needs. We look forward to welcoming you to our family!
No. The path to the plugin JAR file or class path gets saved to the user plugin configuration XML file. The Plugin Manager will load it dynamically upon the application start. If you however move the tool into another folder, you need to either add the plugin JAR to the Java class path or plug it in again.
No. So called “built-in plugins” represent core classes from the product JAR binaries and they cannot be uninstalled. They can be however disabled through installation of a plugin which implements the same functionality.
Just copy it to the folder where you installed the tool to. It will pick it up after restart and make it available in the Language drop down of the Login Dialog.
The most commonly used verification methods are:
Advanced image detection algorithms allow Robot scripts to verify whether an item is present on the visible display, or not, within fractions of a second. Dynamic wait times mean no unnecessary delays to your execution.
Through OCR or image based text recognition T-Plan Robot can identify text displayed on the screen and make it available for you to use thereafter. This feature can be used to verify that a particular word or phrase is present or simply to log what text is being displayed.
Numerous environments can be automated, including Windows, Mac, Linux, Desktop applications, Web applications, Flash, Flex, HTML5 and many more.
Mobile phones and tablets are also supported for Android, iOS and Windows Phone.
For more information please see our summary page.
Our advanced recorder makes the task of scripting a quick and simple job. Simply connect to your target environment, activate the recorder and perform your desired actions. Once complete, review the generated script actions and amend them if necessary before re-executing it.
Generating scripts and actions through the recorder makes automation accessible to those with even the most modest experience.
For more information please see our Script Recorder page.
Automation scripts can currently be created in both of the following formats:
The TPR format is T-Plans proprietary scripting language. Following a basic principle of “<command> <parameter>” while using simple English command names, such as Click, Swipe, Type, Log, Screenshot, etc, means that this is a very intuitive and easy to follow language.
An example of a TPR script is as follows:
Click image template=Browser
Type “I love T-Plan Robot”
Click image template=Search
Log “Test Completed.”
Java formatted scripts can be generated and edited within Robot using the same features and functionality as standard TPR scripts. Alternatively Java scripts can be created and edited in 3rd party Java editors such as NetBeans and Eclipse.
Finally TPR scripts can be exported into Java format if needed however both formats can call and reference scripts of the other format.
Got your own Question? Here are some options:
Here are several ways to contact us