ObolNetwork / ObolNetwork/distributed-validator-specs
Test report - suggestion
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Hi guys,
Long time no see 😃
I took a look at your repo, and I have one suggestion of a useful addition in regards to testing.
To see the value in testing a reporting is needed. Otherwise when something fails it takes you more time to detect root cause of an issue.
I would suggest to look into implementation that I did on the API repo where we have in the workflow test report within the Open PR, within workflow itself and a test report with unique url of that run. It helps for visibility
Test reporting tool suggested: Allure Report
Peace ✌️
Contributor guide
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
Start by reviewing the repository's existing test workflow and the reporting implementation in the referenced API repository. Done means test results are visible in the open pull request and workflow, with a unique URL for each run using Allure Report.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100