JUnit XML View
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 341
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm considering implementing some performance testing in my deployment pipeline, and therefore i'm considering xhprof, i'm already using it in my development environment, so it's a familiar tool to me.
I'm considering to implement a JUnit xml view, so that it can be use inside of jenkins, so see if the performance changes over time, on a predefined set of visited URL's at the website.
Do you have any notes to add to this, and how do you like the idea?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, entry points, or exact output requirements are named. Review xhgui's existing view structure and how its profiling data is exposed, then confirm Jenkins' JUnit XML expectations; done means a defined, tested view that represents performance results for selected URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- ci-cd, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100