surok112 / robotframework-maven-plugin Goto Github PK

Please update the dependencies, so that the latest RF release (v 2.6.3) will be 
used.

Running

mvn test

fails on my own Linux machine, since VerifyMojoTest is executed before 
AcceptanceMojoTests and the former fails because it is dependent on the output 
of the latter. 

I propose to use fixed, predefined data in VerifyMojoTest. The XML output 
format is stable enough, so this should be safe.

The plugin doesn't really use the jybot script. "run" goal sounds more 
appropriate

This might be a problem for a mailing list, but at the moment we have none, so 
I post this here.
I do not understand how I can include tools.jar to the classpath when running 
the libdoc goal for Java test libraries, and the test does not find it either. 
Within a maven run, tools.jar should be on the classpath, so I do not 
understand why the error message appears.


What steps will reproduce the problem?
1. Check out
2. Run the tests

What is the expected output? What do you see instead?
Tests should pass
But the output is:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running com.googlecode.LibDocMojoTest
Creating documentation from Java source files requires 'tools.jar' to be in CLAS
SPATH.

Try --help for usage information.
Resource file 'src\test\java\com\googlecode\html_resource.txt' doesn't exist.
..
Results :

Failed tests:
  testShouldSucceed(com.googlecode.LibDocMojoTest)

Tests run: 4, Failures: 1, Errors: 0, Skipped: 0

What version of the product are you using? On what operating system?
1.1-SNAPSHOT

noncritical tests are written also as failures in xunit output and this causes 
further tooling to determine the test completely failed even when none of the 
critical test were failing.

I suggest that these tests are written (optionally) as skipped instead if 
that's not used already for other purposes. skipped tag seems to have type 
field that I think junit uses to output the reason declared @Ignore annotation. 
Maybe that could be used to refer to the tag(s) that caused the test to be 
noncritical in the first place. I can't find a proper way to present the 
error/failure message, but at least I can live without it since error logs 
contain it as well.

--
Tuomas

The listener argument is passed as "--listeners" but instead should be 
"--listener". Using the listeners right now causes an error in the build.

What steps will reproduce the problem?

1. Create a POM file that includes a) robotframework-maven-plugin as a <plugin> 
and b) SaxonB 9.1.0.8 
(http://mvnrepository.com/artifact/net.sourceforge.saxon/saxon/9.1.0.8) as a 
<dependency>.
2. Run Maven so that robotframework-maven-plugin is executed.
3. Check out the log file.

What is the expected output? What do you see instead?

[INFO] --- robotframework-maven-plugin:1.1.1:run (default) @ modulename ---
[ ERROR ] Unexpected error: SAXException: Parser configuration problem: 
namespace reporting is not enabled

What version of the product are you using? On what operating system?

Version: robotframework-maven-plugin 1.1.1
Operating system: Linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 
2011 i686 i686 i386 GNU/Linux

Please provide any additional information below.

If I remove the Saxon dependency, the error disappears, but Saxon is a required 
dependency for this project, unfortunately.

This might also be a bug in Saxon rather than robotframework-maven-plugin...?

What steps will reproduce the problem?
1. Create test with selenium library keyword
2. Run


What is the expected output? What do you see instead?
Selenium test should run.
Instead, I get:
"Suite setup failed:
No keyword with name 'Start Selenium Server' found.

Also suite teardown failed:
No keyword with name 'Stop Selenium Server' found."
Obviously the selenium library cannot be found. 

Is there a way to provide it automatically without manual installation of the 
selenium library?
I would also require other libraries, such as the database library. How can I 
do this?

What version of the product are you using? On what operating system?
1.0.1
Windows

Please provide any additional information below.

Robot Framework creates report and log files automatically. To disable them, 
special value NONE must be passed to --report and --log. However, when using 
e.g. <log>NONE</log> with the maven plugin, the log file is created to 
${outputDirectory}/NONE.html

For tests that depend on environement vars (e.g. LD_LIBRARY_PATH) it would be 
handy to have a surefire-line environment variable setting ability.

Console shows classes can't compile during libdoc goal invocation. Looks like 
it can't see beyond itself.

Nonetheless, libdoc still works as correct compilation is not needed to create 
documentation.

Please provide a property to tweak PYTHONPATH, for Robot libraries which import 
external libraries.

libdoc.py has a nice --pythonpath option for that.

See if we can integrate the reports being generated by RF to the Maven 
reporting mechanism (site perhaps)

Since Robot Framework 2.7 changed the libdoc usage quite a bit, supporting 
`<libraryOrResourceDirectory>` would require some additional work. Getting any 
kind of 2.7 compatible release ready is more important, so I suggest dropping 
this feature.

It can be restored later, if required.

Keyword libraries inside src/test/java are not in the classpath when jybot goal 
is run

Currently, the plugin expects the excludes,includes and criticalTags as a List. 
I want to request for a way to pass these tags as a comma-delimited string.

In our solution, the user needs to specify the test tags when he is running 
tests via some scripts. As far as I know, maven does not allow system 
properties of List type to be set from command line without changing the pom 
file. But if the input is a comma-delimited string we can easily set it via 
command line.

Hope that explains the problem we are facing.

What steps will reproduce the problem?
1. Have over 60 test suites and 100 test cases.
2. Upgrade com.googlecode.robotframework-maven-plugin from 1.1.1 to 1.1.2

What is the expected output? What do you see instead?
Expect to run test suites on the maven-robotframework and for report to be 
generated on hudson.  This works fine fore version 1.1.1 but for version 1.1.2 
it generates the following error:

java.lang.OutOfMemoryError: GC overhead limit exceeded
        at org.python.core.PyBaseCode.call(PyBaseCode.java:196)
        at org.python.core.PyFunction.__call__(PyFunction.java:370)
        at org.python.core.PyFunction.function___call__(PyFunction.java:375)
        at org.python.core.PyFunction.__call__(PyFunction.java:365)
        at org.python.core.PyObject._callextra(PyObject.java:537)
        at xml.parsers.expat$py.new_method$20(/home/tomcat/.m2/repository/org/robotframework/robotframework/2.6.3/robotframework-2.6.3.jar/Lib/xml/parsers/expat.py:247)
        at xml.parsers.expat$py.call_function(/home/tomcat/.m2/repository/org/robotframework/robotframework/2.6.3/robotframework-2.6.3.jar/Lib/xml/parsers/expat.py)
        at org.python.core.PyTableCode.call(PyTableCode.java:165)

it is a bit difficult to use if you keep resources and tests in the same 
folder, which seems to be a common practice. Libdoc cannot handle test cases, 
only resources. A future improvement might be to have a fileset with includes 
and excludes which runs against the default tests folder. I'll write an issue 
for that and see if I can come up with something.

Hi team,
I'm developing a robotframework eclipse plugin using this maven plugin. We need 
to pass some arguments such as testCasesDirectory from commandline using 
"-DtestCasesDirectory=${somePath}". Could you please add this feature?

I have already made the change and the attached is the patch.

Thank you very much.

When I run the plugin to create doc, I am getting this error:

[ERROR] Failed to execute goal 
com.googlecode.robotframework-maven-plugin:robotframework-maven-plugin:1.1.2:lib
doc (default-cli) on project jive-robot-framework: Failed to execute libdoc 
script: PyException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
com.googlecode.robotframework-maven-plugin:robotframework-maven-plugin:1.1.2:lib
doc (default-cli) on project jive-robot-framework: Failed to execute libdoc 
script
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute 
libdoc script
    at com.googlecode.LibDocMojo.subclassExecute(LibDocMojo.java:70)
    at com.googlecode.AbstractMojoWithLoadedClasspath.execute(AbstractMojoWithLoadedClasspath.java:46)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
    ... 19 more
Caused by: Traceback (most recent call last):
  File "<iostream>", line 74, in <module>
ImportError: No module named serializing

    at org.python.core.PyException.fillInStackTrace(PyException.java:70)
    at java.lang.Throwable.<init>(Throwable.java:181)
    at java.lang.Exception.<init>(Exception.java:29)
    at java.lang.RuntimeException.<init>(RuntimeException.java:32)
    at org.python.core.PyException.<init>(PyException.java:46)
    at org.python.core.PyException.<init>(PyException.java:43)
    at org.python.core.PyException.<init>(PyException.java:61)
    at org.python.core.Py.ImportError(Py.java:290)
    at org.python.core.imp.import_logic(imp.java:785)
    at org.python.core.imp.import_name(imp.java:839)
    at org.python.core.imp.importName(imp.java:884)
    at org.python.core.ImportFunction.__call__(__builtin__.java:1220)
    at org.python.core.PyObject.__call__(PyObject.java:357)
    at org.python.core.__builtin__.__import__(__builtin__.java:1173)
    at org.python.core.imp.importFromAs(imp.java:978)
    at org.python.core.imp.importFrom(imp.java:954)
    at org.python.pycode._pyx0.f$0(<iostream>:718)
    at org.python.pycode._pyx0.call_function(<iostream>)
    at org.python.core.PyTableCode.call(PyTableCode.java:165)
    at org.python.core.PyCode.call(PyCode.java:18)
    at org.python.core.Py.runCode(Py.java:1261)
    at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:235)
    at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:230)
    at com.googlecode.LibDocMojo.runLibDoc(LibDocMojo.java:140)
    at com.googlecode.LibDocMojo.documentLibraryOrResourceDirectory(LibDocMojo.java:109)
    at com.googlecode.LibDocMojo.subclassExecute(LibDocMojo.java:64)
    ... 22 more
[ERROR] 
[ERROR] 

What steps will reproduce the problem?
1. Run the plugin with Java 5 (Java Home = 1.5 JDK)
2. Error is shown: String.isEmpty: no such method

What is the expected output? What do you see instead?
Should work with Java 1.5 (unfortunately, we can not upgrade any time soon)
Please use the following in the POM, it seems to work flawlessly, at least with 
the trunk sources.

<plugin>
    <inherited>true</inherited>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <source>1.5</source>
        <target>1.5</target>
    </configuration>
</plugin>

What version of the product are you using? On what operating system?
1.1-SNAPSHOT

In our usage of framework on the UI testing, a lot of time we need to retry the 
failed testsuites. So can you add the feature?  Currently I am adding some code 
in the AcceptanceTestMojo.java to allow user decided how many time retry they 
want.  Is that possible to put this into the plugin?  Since this is very 
important feature for us.




protected void subclassExecute() throws MojoExecutionException, 
MojoFailureException {

    if (shouldSkipTests()) {
        getLog().info("RobotFramework tests are skipped.");
        return;
    }
    String[] runArguments = generateRunArguments();


        getLog().info("robotframework arguments: " + StringUtils.join(runArguments, " "));

    int robotRunReturnValue = RobotFramework.run(runArguments);

    /**
     * added by shawna.qian
     * retry the testsuites having failed testcases
     */
    getLog().info("robotRun return code="+ robotRunReturnValue);
    getLog().info("requestedRetryCount="+ requestedRetryCount);

    int retry = 0;
    int iRequestedRetryCount = Integer.parseInt(requestedRetryCount);
    while(robotRunReturnValue >0 && retry < iRequestedRetryCount)
    {
      retry ++;
      getLog().info("retry execution count = " + retry + " times");

      robotRunReturnValue = RobotFramework.run(runArguments);
      getLog().info("retry execution count = " + retry + " time:  robotRun return code="+ robotRunReturnValue);

    }
    /**
     * end of the retry
     */


    evaluateReturnCode(robotRunReturnValue);


}
/**
 * added by shawna.qian
   * The number of retry the user can set when test suites have failed testcases:  only the last one gets reported ; all tests will be re-executed
   * by default it will not be retried
   * @parameter default-value="0"  expression="${maven.test.retry}"
   */
 private String requestedRetryCount;

* I am using 3.0.0-SNAPSHOT on windows (It has fix for Issue 21)
* I have around 1500 test cases, and output xml thus created is around 100 MB 
in size.
* As robot takes lot of time and memory to parse that, I tried to use the fix 
given at 
http://code.google.com/p/robotframework-maven-plugin/issues/detail?id=21, to 
disable logs and reports. Intention was to disable report generation by maven 
plugin and then using 'rebot' to do it for me.
* However, although log and report html are not created now, but still I get 
the out of memory error, because robot tries to create Xunit file.
* Page 
http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.ht
ml#xunit-compatible-result-file states, that this file is created *only* when 
"--xunit" is passed to robot. 
* Is there a way to disable generation of Xunit also completely, to make robot 
to stop processing 'ouput.xml' completely? 
* Also, is there a way to stop generation of log and report html files in 1.1.2 
version of maven plugin also? Or it can't be done at all because of Issue 21?


Regards,
Ramender Mall

I tried to use SeleniumLibrary as external libraries as described, but robot 
can not find it. The PYTHONPATH seems to be invalid, instead of \ there is 
always \\

I'm using windows XP with maven 3.0.3 and plugin version 1.1.1

What steps will reproduce the problem?
1. Run selenium tests with the rf mvn plugin
2. The tests pass, however, the following output is shown:

Output:  c:\az_daten\workspaces\oksc-2.0.x\oksc-selenium\target\robot\output.xml

Exception in thread "_CouplerThread-4 (stdout)" Traceback (most recent call last
):
  File "\maven-2.0\repository\local\org\robotframework\robotfra
mework\2.5.5\robotframework-2.5.5.jar\Lib\subprocess.py", line 679, in run
  File "\maven-2.0\repository\local\org\robotframework\robotfra
mework\2.5.5\robotframework-2.5.5.jar\Lib\subprocess.py", line 679, in run
ValueError: I/O operation on closed file
Report:  \workspaces\oksc-2.0.x\oksc-selenium\target\robot\report.htm
l
Log:     \workspaces\oksc-2.0.x\oksc-selenium\target\robot\log.html


What is the expected output? What do you see instead?
No errors should be shown.

What version of the product are you using? On what operating system?
1.1-SNAPSHOT

Please provide any additional information below.
The output.xml is written anyway.

What steps will reproduce the problem?
1. Replace SeleniumLibrary with the supposedly drop-in replacement 
Selenium2Library

What is the expected output? What do you see instead?
[ ERROR ] Invalid syntax in file 
'/home/development/src/test/resources/robotframework/tests/scripts.txt' in 
table 'Settings': Importing test library 'Selenium2Library' failed: 
ImportError: No module named api

What version of the product are you using? On what operating system?
1.1.1 running on Ubuntu

Please provide any additional information below.
These tests work if I run them directly from RIDE. When running using the Maven 
plugin I get this error.

Provide a way to document dynamic API libraries, such as those provided by 
JavaLib Core.

In an effort to see if this is possible I attached this plugin to the test 
Maven phase and modified the parameters being passed to libdoc in a debugger 
and ran into issues where the dependencies normally available in the test phase 
(in JUnit, etc.), are not. Implementing this would require setting the 
classpath correctly.

Majority of maven plugin intended to run integration test allow specifying 
system properties.

For example surefire plugin has following configuration:

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.8</version>
        <configuration>
          <systemPropertyVariables>
            <propertyName>propertyValue</propertyName>
            <buildDirectory>${project.build.directory}</buildDirectory>
            [...]
          </systemPropertyVariables>
        </configuration>



It would be great if maven robot plugin would allow also passing system 
properties.
Of course robot has --variable option, but it is not passed to java system 
property.