-
Improvement
-
Resolution: Done
-
Minor
-
Robot Framework plugin 3.0.1
-
-
3.2
Currently the Robot Framework plugin REST API returns a response for the RobotResult model
{ criticalFailed: criticalPassed: criticalTotal: executedSuites: failedCases: [] overallFailed: overallPassed: overallSkipped: overallTotal: passPercentage: skipPercentage: timestamp: }
It would be useful for the response to include
passedCases: [] skippedCases: []
The failedCases is obtained from the RobotResult.getAllFailedCases() method, which returns List<RobotCaseResult>, which is iterated through and the RobotCaseResult.getName() and RobotCaseResult.getParent() methods are used to create the List<String> failedCases
The RobotResult.getAllCases() also returns List<RobotCaseResult> and similarly, the List<String> passedCases and List<String> skippedCases could be created with the getName() + getParent().
Each RobotCaseResult would be checked with .isPassed() or isSkipped() for their respective List<String>
The last work done for the failedCases value https://github.com/jenkinsci/robot-plugin/pull/24/files#diff-a4d1d7fb1980ff4c5825099d9be03cd49f2fd1bcf5f8621926764468315064c2
- relates to
-
JENKINS-22546 Add REST API to robot framework plugin
-
- Closed
-
[JENKINS-67683] Add a build's test cases to REST API response
Link |
New:
This issue relates to |
Description |
Original:
Currently the Robot Framework plugin REST API returns a response for the RobotResult model
{code:java} criticalFailed: criticalPassed: criticalTotal: executedSuites: failedCases: [] overallFailed: overallPassed: overallSkipped: overallTotal: passPercentage: skipPercentage: timestamp:{code} It would be useful for the response to include {code:java} passedCases: [] skippedCases: []{code} The failedCases is obtained from the RobotResult.getAllFailedCases() method, which returns List<RobotCaseResult>, which is iterated through and the RobotCaseResult.getName() and RobotCaseResult.getParent() methods are used to create the List<String> failedCases The RobotResult.getAllCases() also returns List<RobotCaseResult> and similarly, the List<String> passedCases and List<String> skippedCases could be created with the getName() + getParent(). Each RobotCaseResult would be checked with .isPassed() or isSkipped() for their respective List<String> The last work done for the failedCases value https://github.com/jenkinsci/robot-plugin/pull/24/files#diff-a4d1d7fb1980ff4c5825099d9be03cd49f2fd1bcf5f8621926764468315064c2 |
New:
Currently the Robot Framework plugin REST API returns a response for the RobotResult model
{code:java} { criticalFailed: criticalPassed: criticalTotal: executedSuites: failedCases: [] overallFailed: overallPassed: overallSkipped: overallTotal: passPercentage: skipPercentage: timestamp: }{code} It would be useful for the response to include {code:java} passedCases: [] skippedCases: []{code} The failedCases is obtained from the RobotResult.getAllFailedCases() method, which returns List<RobotCaseResult>, which is iterated through and the RobotCaseResult.getName() and RobotCaseResult.getParent() methods are used to create the List<String> failedCases The RobotResult.getAllCases() also returns List<RobotCaseResult> and similarly, the List<String> passedCases and List<String> skippedCases could be created with the getName() + getParent(). Each RobotCaseResult would be checked with .isPassed() or isSkipped() for their respective List<String> The last work done for the failedCases value [https://github.com/jenkinsci/robot-plugin/pull/24/files#diff-a4d1d7fb1980ff4c5825099d9be03cd49f2fd1bcf5f8621926764468315064c2] |
Description |
Original:
Currently the Robot Framework plugin REST API returns a response for the RobotResult model
{code:java} { criticalFailed: criticalPassed: criticalTotal: executedSuites: failedCases: [] overallFailed: overallPassed: overallSkipped: overallTotal: passPercentage: skipPercentage: timestamp: }{code} It would be useful for the response to include {code:java} passedCases: [] skippedCases: []{code} The failedCases is obtained from the RobotResult.getAllFailedCases() method, which returns List<RobotCaseResult>, which is iterated through and the RobotCaseResult.getName() and RobotCaseResult.getParent() methods are used to create the List<String> failedCases The RobotResult.getAllCases() also returns List<RobotCaseResult> and similarly, the List<String> passedCases and List<String> skippedCases could be created with the getName() + getParent(). Each RobotCaseResult would be checked with .isPassed() or isSkipped() for their respective List<String> The last work done for the failedCases value [https://github.com/jenkinsci/robot-plugin/pull/24/files#diff-a4d1d7fb1980ff4c5825099d9be03cd49f2fd1bcf5f8621926764468315064c2] |
New:
Currently the Robot Framework plugin REST API returns a response for the RobotResult model
{code:java} { criticalFailed: criticalPassed: criticalTotal: executedSuites: failedCases: [] overallFailed: overallPassed: overallSkipped: overallTotal: passPercentage: skipPercentage: timestamp: }{code} It would be useful for the response to include {code:java} passedCases: [] skippedCases: []{code} The failedCases is obtained from the RobotResult.getAllFailedCases() method, which returns List<RobotCaseResult>, which is iterated through and the RobotCaseResult.getName() and RobotCaseResult.getParent() methods are used to create the List<String> failedCases The RobotResult.getAllCases() also returns List<RobotCaseResult> and similarly, the List<String> passedCases and List<String> skippedCases could be created with the getName() + getParent(). Each RobotCaseResult would be checked with .isPassed() or isSkipped() for their respective List<String> The last work done for the failedCases value [https://github.com/jenkinsci/robot-plugin/pull/24/files#diff-a4d1d7fb1980ff4c5825099d9be03cd49f2fd1bcf5f8621926764468315064c2] |
Assignee | Original: jpiironen [ jpiironen ] | New: Aleksi Simell [ aleksisimell ] |
Labels | New: robocon2022 |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Resolution | New: Done [ 10000 ] | |
Status | Original: In Review [ 10005 ] | New: Fixed but Unreleased [ 10203 ] |
Released As | New: 3.2 | |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |