-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: resultProcessor #117
Conversation
many thanks @axules for updating! btw, I just pushed some changes, would you mind fixing the conflicts? |
refactor: add links to Testrail doc to clarify custom fields config refactor: wrap text into anchor element refactor: add anchor to readme refactor: after code review fix: test title Co-authored-by: kobenguyent <[email protected]> feat: tests feat: use resultProcessor result for testrail chore: readme.md feat: add resultProcessor chore: get rid of unused deps Co-authored-by: Denis Shelest <[email protected]>
@kobenguyent It has to be fine. |
aha, as we have actually 2 workflows, but only one workflow would be triggered on PRs. |
Thanks @axules! |
🎉 This PR is included in version 1.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Add
resultProcessor
to plugin config. It has to be a function, which will be called for each result, just before sending result to testrail.It is needed to provide possibility to customize result object before sending it to testrail. To resolve this: