Ride, the run plugin custom script and using log and report buttons

[Tatu aalto]

Ugh

I am using Ride 0.45 in windows 7. When I have a custom scrip, in the Execution Profile, is it possible to make Ride to know that report and log files are stored in some folder? So that I could just press Report and Log buttons in the Run-tab to open the html files?

-Tatu 

[Mikko Korpela]

Hi Tatu,

What kind of custom script do you have?

Key thing is that the custom script should delegate all the command line arguments from RIDE to the pybot / jybot script.

This way the runner listener will get the information where the log and report file are located - thus the log and report file buttons will work.

Kind Regards,

Mikko Korpela

[Tatu aalto]

Ugh

It is simple scipt.
- It makes a cd command to correct folder
- Then it executes maven command: mvn clean verify

The pom.xml contains the Robot Framework Maven plugin and some other definitions, which are responsible to execute test suites.

-Tatu

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/robotframework-users/-/K94OGEJJ40AJ.
To post to this group, send email to robotframe...@googlegroups.com.
To unsubscribe from this group, send email to robotframework-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/robotframework-users?hl=en.

[dschulten]

Hi Tatu,

a -Dlistener option could be used to tell the maven plugin who the listener is so that it runs jybot with the appropriate --listener argument.

However, when RIDE runs a custom script, it passes the Socketlistener path and a dynamically determined port to the custom script. I see two possibilities here:

1. If RIDE could be told to listen on a specific port, e.g. in settings, this information could be given to the maven plugin in the pom via the existing listener configuration element in V1.1.2. Can the RIDE experts tell us if that can be done?

2. The maven plugin can be changed to take -Dlistener on the commandline, then you could do something like
mvn verify -Dlistener=%4 in your custom script, as long as the fourth argument passed by RIDE is actually the listener, which currently seems to be the case.

Actually, the latter is quite easy. I have added a listener as an expression to the maven plugin in the current 3.0.0-SNAPSHOT. If you want, you can check out from http://code.google.com/p/robotframework-maven-plugin/source/checkout, run mvn install. Then you can use the new version in your project:

      <plugin>
        <groupId>com.googlecode.robotframework-maven-plugin</groupId>
        <artifactId>robotframework-maven-plugin</artifactId>
        <version>3.0.0-SNAPSHOT</version>
      ...

The new version also uses RF 2.7.2 internally.

Best regards,
Dietrich

[Tatu Aalto]

Ugh

I did go with the option 2 and did get the plugin with mvn install command.  I did modify my script to this: mvn clean verify -Dlistener=%4 and then the ride is able to open the log and report files. With my small test set, this is ready to go, hopefully when release is made, it is documented somewhere.

But there was one hick up. It seems that folder were test are located is changed between the versions (1.1.2 -> 3.0.0-SNAPSHOT). In the 1.1.2 version my test were located in the trunk\src\test\resources\robotframework\tests and I do not have the testCasesDirectory parameter defined in the pom.xml. In the 3.0.0-SNAPSHOT version, plugin assumes that test are located in the \trunk\src\test\robotframework\acceptance folder. I am just wondering, is this by purpose or is it accident/development phase thing.

But thanks from fast response and now I eagerly waiting for the 3.0.0 released version.

-Tatu

--

You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/robotframework-users/-/CC6VD9opWsIJ.