Skip to content

JENKINS-75980 : Add Skipped Tests results in a separate section in the Browse Results Screen#87

Merged
asimell merged 1 commit intojenkinsci:masterfrom
AdityaKeshan:Add_Skipped_Section
Aug 22, 2025
Merged

JENKINS-75980 : Add Skipped Tests results in a separate section in the Browse Results Screen#87
asimell merged 1 commit intojenkinsci:masterfrom
AdityaKeshan:Add_Skipped_Section

Conversation

@AdityaKeshan
Copy link
Copy Markdown
Contributor

Added Skipped Results in a separate section in the Browse Results Screen. This includes display of "Age" for the skipped tests. This issue was raised under JENKINS-75980 : Add Skipped Tests results in a separate section in the Browse Results Screen

Testing done

Before Changes:
image

After Changes:
image

  • This was tested with creating a pipeline job that parses an output.xml at the end, this test contained skipped test and we verified the age and the listing of the same on the browse page

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests that demonstrate the feature works or the issue is fixed

Copy link
Copy Markdown
Contributor

@asimell asimell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, @Tattoo any comments?

@AdityaKeshan
Copy link
Copy Markdown
Contributor Author

@asimell, I have a question, how does this project undergo deployment/release? Just curious about it. Do we have a release pipeline for the same?

@asimell
Copy link
Copy Markdown
Contributor

asimell commented Aug 13, 2025

@AdityaKeshan Deployment/release is relatively arbitrary. We're more just maintaining the plugin with relatively few new features focusing more on bug fixes and keeping the plugin relevant with new Robot Framework versions.

We do monitor PRs and the issue tracker and I'm trying to address each submitted ticket relatively quickly – excluding holiday periods. We usually want to add a bit more than just a single fix or small feature per release, but we also don't want to keep merged features/bug fixes unreleased for too long. Once we have some merged PRs, we wait for a week or so to see if any new stuff is incoming and then release.

@AdityaKeshan
Copy link
Copy Markdown
Contributor Author

I see thanks for the explanation. 😄

@asimell asimell merged commit 24bf419 into jenkinsci:master Aug 22, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants