Robot spoils SUT environment

[GoogleCodeExporter]

Issue Version:
javalib-core version- All
jvm -All
Operating System - Windows..

I would like to address some of the "serious" problems with Robot framework.

This is about the Robot Framework spoiling the application environment and
hiding/creating faults with the application.

Normally JVM Connector, Swing Library comes with lot of OEM's bundled inside.

Problems Observed:

1. When a SUT uses same OEM but different version of it, problem observed
in launching/functionality of the application
(i.e this observed with "avlon framework" where Swing/JVM connector uses
the older versions.)

2. When a SUT and Robot uses same OEM, but by mistake the OEM is not
packaged with SUT. In this case in a manual run of the application, the
application would fail due to missing of the OEM.

But when it is started with Robot Framwork "for Testing" it would hide the
error by providing the unpakaged OEM to the SUT to use and  hides a
"Critical fault"

These cases makes Robot Framework not reliable in Testing point of view,
why we are really spending the effort.

In my opinion the Robot Framework should be Thin and should not spoil the
SUT environment.

With Regards
Arul

Original issue reported on code.google.com by [email protected] on 14 Jan 2010 at 3:19