The most recent release of JavaStar is the one available on our web site. This release is compatible with all JDK 1.1.x virtual machines prior to and including the release number. For example, JavaStar 1.1.5 is compatible with JDK versions 1.1.1 through 1.1.5.
Get compiling error when using JDK1.2 and JavaStar 1.2.
Current workaround is to modify the project settings under the "java" tab to point to /jdk1.2/bin/javac instead of the default java compiler (i.e. /jdk1.2/jre/bin/javac).
What platforms does JavaStar run on?
JavaStar runs on any platform that runs a Java Virtual Machine (JVM) that is JDK 1.1.x compliant.
I'm running on a Mac. Can I use JavaStar?
No. As of this time, the JVM that runs on MacOS is not JDK 1.1.x compliant and therefore will not work with JavaStar.
How do I download and install JavaStar?
You can download a time-limited evaluation copy of JavaStar from the download page on the SunTest web site. Once you fill out the Registration Form, you'll be presented with download and installation information.
When you purchase JavaStar, you are provided with instructions on how to download and install the full version of the product.
Which versions of the JDK do I need to run JavaStar?
For JavaStar 1.1.1, you need JDK 1.1.1 For JavaStar 1.1.2, you can use JDK 1.1.2 or 1.1.3 For JavaStar 1.1.4 (and later) you can use JDK 1.1.x (where x = an integer up to the version of JDK you are using...if you are using JDK 1.1.4, you can use JavaStar 1.1.1 through JavaStar 1.1.4, etc.)
We do encourage you to install the latest release of both JDK and JavaStar (since these versions will have more bugs fixed and improved functionality).
The application (or applet) under test does not need to be developed in the JDK 1.1.x environment, but you must be able to run it in a JDK 1.1.1 (or higher) environment. For instance, you may have an application that was developed under JDK 1.0.2, that you can run using the JDK 1.1.1. This application can be tested using JavaStar.
If the latest JDK was just released, we may not yet have released an upgrade (it takes approximately 4 weeks from the release of a new JDK to the release of a new JavaStar).
The application I am testing was developed using an earlier version of the JDK. Can I use JavaStar to test it?
If your application runs under JDK 1.1.1 or later, then you can test it using JavaStar.
Can I test my application using the Netscape Navigator Browser?
JavaStar
uses special features available in the JDK 1.1.1 (or later). Currently,
the Netscape browser is not 1.1.1, and so tests will not play back correctly
in this environment. We expect Netscape to release a version which is 1.1.1
compatible in the not-too-distant future. Watch this web site for announcements.
Can
I test my application using the Internet Explorer Browser?
No. Currently the Internet Explorer uses a non-standard AWT. This non-standard AWT inserts additional layers into the class structure and prevents JavaStar from being able to interact with the applet and the Internet Explorer. Until Microsoft decides to use the standards, we will not be able to release a version of JavaStar that is capable of running with the Internet Explorer.
Yes,
you can test applets using the applet viewer or using the HotJava browser.
Can I test my application across a network?
The answer to this is going to depend on what is meant by across a network. If the script is going to be run on the local CPU, then yes, you can do this. If the script (or JavaStar) is going to be run on another system, and displayed on a local machine, this may not work correctly. If you want to test the client/server interaction, this is covered by JavaStar's abilities.
The following text files are provided with JavaStar:
How can I get a hard copy of the documentation?
You can print the documentation from the PDF version on our website. See the documentation index for more information.
I've
got some comments about the documentation. How do I send these in?
To
submit feedback on the documentation, please fill out the online
Documentation
Feedback form, available on our web site.
Are classes available in testing with JavaStar?
Yes. Please send email to suntest.training@central.com for information on current course offerings.
How do I contact Technical Support?
Send
email to:
javastar-feedback@suntest.com
For users who have not yet purchased the product, this email addression
provides best-effort respond as time permits. If you purchase a support
contract, you will be given alternate directions on how to submit requests
for technical support.
How
do I submit bug reports or enhancement requests?
Use
the online
form on the SunTest web site for submitting bug reports and suggestions.
Bongo, IFC, JFC, and Symantec Cafe have been used by customers (along with others) and have not generated compatibility issues that were JavaStar related.
When using RogueWave's JWidgets, you will need to use the non-component locator available in JavaStar 1.1.4 and above.
Does JavaStar support JFC(Java Foundation Classes), a.k.a. Swing? Is there a locator for JFC?
JavaStar will fully support JFC in the future. In the interim, we have created and made available a Non-Component Locator that can be used with JavaStar 1.1.4 and later to use Swing components (in particular, JTreee and JTable components. This NCL is part of the standard JavaStar distribution, and can be found under the "contrib" directory.
You need to set your CLASSPATH variable to
include the javastar.zip file as the first file in your CLASSPATH.
When I try to create a script for my application, I get an error trying to start the application ("There is some problem accessing your application").
Usually, this occurs because your application is not in the CLASSPATH or the fully qualified name was not used.
If you are use the browse facility to point to the class for your application,
it will automatically add it to your classpath for that session. You
will need to add the path to your application to "Additional Classpath"
under Set Options/Environment for it to be permanent.
How do I set classpath?
You need to set the classpath to include javastar and your application.
On Windows/DOS:
set CLASSPATH=<path>;<path> . . .
On Solaris, csh:
setenv CLASSPATH=<path>:<path> . . .
On Solaris, non-csh
CLASSPATH=<path>:<path>: etc
export CLASSPATH
Note: different directory delimiters are used on Solaris and
Windows.
Example: If you have javastar installed in c:\javastar, and your
application to test is under c:\myapp.
(and you're on windows):
set CLASSPATH=c:\javastar\javastar.zip;c:\myapp
If your application is in a zip file, you can refer to it directly as
a zip file
(e.g. set CLASSPATH=c:\javastar\javastar.zip;c:\myapp\myapp.zip).
I get dialog saying "Error reading license file" when I start JavaStar, I then clicked on the "OK" button and it just hangs.
This usually means that one has downloaded and installed as root, then tries to start tool as a particular user or has installed as a user and tries to start tool with a different user. In each case permissions are wrong. The solution is to install tool as a user and start the tool with same user so that the permissions are correct.
What if I am getting an error that the file is corrupt or read-protected?
Typically, this is an error involving your CLASSPATH. Check to make sure you can launch it normally with java. If this works, your classpath may require adjustment. (It's finding something at the wrong time in the search.)
Use <Ctrl-Alt-F7> or <Ctrl-Shift-F7> to get access to the window's menu. You may also need <Ctrl-Alt-F8> or <Ctrl-Shift-F8> for the step function and <Ctrl-Alt-F9> or <Ctrl-Shift-F9> for the continue function when playing back scripts.
Recording against an authorization or Login dialog suspends processing.
You will normally run into this situation because the authorization or Login dialogs are modal dialogs. See above answer for information on how to control record/playback when modal dialogs are involved.
You can't. At this time, Java doesn't allow this, therefore, JavaStar can't do it.
Why do recordings sometimes contain coordinates?
Coordinates are passed along from the Java event to the script recording because the information is available. There are some situations where we know the information will not be useful (in which case we pass the center point of the component instead) but in any case where we can't be sure, we forward the information to the script. The coordinates that are passed, are relative to the top left corner of the object the event relates to (e.g. the top left corner of the dialog).
How do I pass arguments to a test?
If running a test from the GUI (and "Run Test" menu button), there is a "Test args:" field to fill in.
If running from the command line, the last option should be "-testargs" followed by a list of arguments which will be passed to the test. You could also use the "-prop" option and provide the name of a property file.
Are canvases supported for Verification?
You can verify an image or use simple methods to verify in more detail. This works with canvases or "panels with images".
What you need to do is use the -mx parameter to give the JVM a larger memory size. For more details on this and other parameters type "java -help".
Example: From the command line.
java javastar -noasyncgc -ms4m -mx40m
This would set the minimum stack size to 4 megabytes, and the maximum stack size to 40 megabytes. The maximum stack size must not exceed the systems memory.