|Re: api recorder problems [message #113793 is a reply to message #111553]
||Mon, 01 October 2007 17:30
| Paul Slauenwhite
Registered: July 2009
Thanks for your interest in the API Recorder. Although Technology
Preview is tested, it is still maturing function sometimes with outstanding
Let me try to address these issues below:
"mike shipkowski" <firstname.lastname@example.org> wrote in message
> I am getting mixed results/bahaviors using the API recorder addon. I am
> using eclipse 3.3 and Java 1.5, I have the 1.5 agent controller installed
> (this seems to be required by the API recorder, all other TPTP stuff seem
> to use the internal agent, why is this??)
The API Recorder is tested and works with both the Agent Controller and
Integrated Agent Controller (IAC).
> I have the lated 188.8.131.52 release installed.
TPTP does have a 184.108.40.206 release. I would assume you are (and recommend)
using the latest
maintenance release (220.127.116.11). See:
> o In most cases the tool simply never generates a test case at all. often
> the associated task being profiled never seems to exit, by this I mean
> application exits but the red square on the console says lit and the task
> never displays as terminated in the profiler view.
I believe this is caused by
https://bugs.eclipse.org/bugs/show_bug.cgi?id=138110#c6. If you are using
4.4.0+, please open a defect for this problem
( https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP%20T esting under
the Test.Agents.Recorder component) with the steps/code to reproduce the
> o All in all I only seem to be able to monitor some Swing based
> applications and the example SimpleStringTest code provided in the
> documentation. Any SWT or RCP or more complex java apps never generate
> testsuites. All of the swing based applications generate JUnit test code
> with syntax errors, a line containing "}};" needs to be removed from
> multiple locations.
Currently, only stand-alone Java applications are supported by the API
Recorder. That is, RCP applications are not supported.
When you launch your SWT application, does the application appear and run to
completion? Is a recording created?
Your issue with a stand-alone SWT application and
Swing application (e.g. Java - Application launch configuration) appears to
defect. After looking at the code generation code, I cannot determine where
extra characters are coming from. Can you attach the generated test suite
> o Using all wildcards in the filtering dialog insures not testsuite will
> be generated, I seem to need to specify a package or nothing is collected.
> Actually I seem to need to have a package ending in a '*' for anything to
Yes, by default everything is excluded. You need to specify which packages,
classes, and methods to be recorded. Complete package, class, and method
names (e.g. no trailing *) have been tested to work. If your does not,
reply with the filter set.
> o I really wish the dialog for generating a testsuite pre selected the
> "testsuite" option not the "no testsuite" option, the only reason for
> using it is to generate a testsuite in thefirst place.
Great feedback. There is no default selection since the dialog is reused.
> Not fussing here, this capability would be very useful to me if it worked.
Thank you. We would be interested in discussing if you would like to
contribute to this component.
> I think I read somewhere that this is probekit based?? Is there any
> associated .probe files I can use instead??
Yes, you can export the probe (File >> Export >> Test >> API Recorder Probe.
Powered by FUDForum
. Page generated in 0.13801 seconds