allure-framework / allure-framework/allure-csharp
Implement Allure event listeners
- Dominant language
- C#
- Stars
- 125
- Forks
- 76
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 18
Description
#### I'm submitting a ...
- [ ] bug report
- [x] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.
#### Motivation
Event listeners are a well-established mechanism to modify Allure data before it's written on disk. Some examples of what can be achieved with it:
- exclude test parameters based on a naming convention
- rename steps
- attach extra files
- ...
While popular scenarios need to be supported via API, the listeners cover sophisticated ones that are user-specific.
#### Other information
See the implementation by [allure-java](https://github.com/allure-framework/allure-java/tree/main/allure-java-commons/src/main/java/io/qameta/allure/listener).
Contributor guide
Research direction
Start by reviewing the Allure Java listener implementation at allure-java-commons/src/main/java/io/qameta/allure/listener and compare its concepts with the C# integration. Determine the C# entry points and API shape needed to modify Allure data before it is written, including parameter filtering, step renaming, and extra attachments; done means these listener use cases are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100