• Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major Major
    • robot-plugin
    • Robot Framework plugin v1.4.2

      It would be usefull if we could obtain some values from REST api like the "Age" of tests detected as failing.

          [JENKINS-22546] Add REST API to robot framework plugin

          jpiironen added a comment -

          I think this could be really useful feature in for many users!

          What would be the most important data for you that you would like to obtain from the API?

          jpiironen added a comment - I think this could be really useful feature in for many users! What would be the most important data for you that you would like to obtain from the API?

          Jose Sa added a comment -

          Primarily we are interested in the “failed test cases” table content as shown in robot reports page, the “all test suites” may also be useful but that is secondary.

          Jose Sa added a comment - Primarily we are interested in the “failed test cases” table content as shown in robot reports page, the “all test suites” may also be useful but that is secondary.

          Code changed in jenkins
          User: Janne Piironen
          Path:
          src/main/java/hudson/plugins/robot/model/RobotResult.java
          http://jenkins-ci.org/commit/robot-plugin/388c437acf6bc478187facda97ac18d04259b513
          Log:
          JENKINS-22546: Added initial api functions to robot result

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Janne Piironen Path: src/main/java/hudson/plugins/robot/model/RobotResult.java http://jenkins-ci.org/commit/robot-plugin/388c437acf6bc478187facda97ac18d04259b513 Log: JENKINS-22546 : Added initial api functions to robot result

          Jose Sa added a comment -

          I've tested this plugin with version 1.5.0 and while the robot general information about the specific build is available (total number of tests, tests passed/failed, pecentage of tests passed), the information about the individual failed test cases is missing.

          Sample output using xml rest api:

          <robotResult>
          <allFailedCase/>
          <allFailedCase/>
          <allFailedCase/>
          <criticalFailed>3</criticalFailed>
          <criticalPassed>27</criticalPassed>
          <criticalTotal>30</criticalTotal>
          <overallFailed>3</overallFailed>
          <overallPassed>27</overallPassed>
          <overallTotal>30</overallTotal>
          <passPercentage>90.0</passPercentage>
          <suite/>
          <timeStamp>20140523 15:24:06.067</timeStamp>
          </robotResult>
          

          I tried adding "?depth=2" or "?depth=3" to see if more information would be displayed on sub-levels but it returned the same output.

          Jose Sa added a comment - I've tested this plugin with version 1.5.0 and while the robot general information about the specific build is available (total number of tests, tests passed/failed, pecentage of tests passed), the information about the individual failed test cases is missing. Sample output using xml rest api: <robotResult> <allFailedCase/> <allFailedCase/> <allFailedCase/> <criticalFailed>3</criticalFailed> <criticalPassed>27</criticalPassed> <criticalTotal>30</criticalTotal> <overallFailed>3</overallFailed> <overallPassed>27</overallPassed> <overallTotal>30</overallTotal> <passPercentage>90.0</passPercentage> <suite/> <timeStamp>20140523 15:24:06.067</timeStamp> </robotResult> I tried adding "?depth=2" or "?depth=3" to see if more information would be displayed on sub-levels but it returned the same output.

          Tatu Aalto added a comment -

          I also have the same problem, when I query result, the json looks like this: 

          allFailedCases': [\{}, \{}, \{}, \{}, \{}, \{}]

           

          Would it be possible to get this fixed? 

          Tatu Aalto added a comment - I also have the same problem, when I query result, the json looks like this:  allFailedCases': [\{}, \{}, \{}, \{}, \{}, \{}]   Would it be possible to get this fixed? 

          I'm guessing this plugin is dead, but I figured I would chime in to let anybody working on it know that the allFailedCases feature would be super helpful.

          Benjamin Hammond added a comment - I'm guessing this plugin is dead, but I figured I would chime in to let anybody working on it know that the allFailedCases feature would be super helpful.

          Ryan Pisano added a comment -

          We would like that as well.

          Ryan Pisano added a comment - We would like that as well.

          Aleksi Simell added a comment -

          The allFailedCases issue was fixed in https://github.com/jenkinsci/robot-plugin/pull/24. Sorry for the delay! We'll try to get a release out asap.

          Aleksi Simell added a comment - The allFailedCases issue was fixed in https://github.com/jenkinsci/robot-plugin/pull/24 . Sorry for the delay! We'll try to get a release out asap.

          Lauren added a comment -

          aleksisimell is there going to be any more work for the robot REST API?

          Is there a way to get the data in the Test Suites table (the failed/passed number of tests and the duration for each suite)

          Is there also a way to get the data for each individual test suite - the Test Case table (which holds the data for name, status, and duration of the test case)

          Lauren added a comment - aleksisimell  is there going to be any more work for the robot REST API? Is there a way to get the data in the Test Suites table (the failed/passed number of tests and the duration for each suite) Is there also a way to get the data for each individual test suite - the Test Case table (which holds the data for name, status, and duration of the test case)

          Aleksi Simell added a comment -

          Hi laurenyj

          The REST API might be improved at some point, but right now we haven't planned on improving it. I might take a look at it once we get the RF 4.0 support released.

          Currently the API doesn't support the requests you asked. Those could be nice additions.

          The reason why I closed the ticket was that the API exists and the issue that was discussed last was fixed some time ago already without any new suggestions/ideas. You could open a new ticket with improvement suggestions to the REST API.

          Aleksi Simell added a comment - Hi laurenyj The REST API might be improved at some point, but right now we haven't planned on improving it. I might take a look at it once we get the RF 4.0 support released. Currently the API doesn't support the requests you asked. Those could be nice additions. The reason why I closed the ticket was that the API exists and the issue that was discussed last was fixed some time ago already without any new suggestions/ideas. You could open a new ticket with improvement suggestions to the REST API.

            aleksisimell Aleksi Simell
            josesa Jose Sa
            Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: