Skip to content
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

add Slack reporter (from jonsamwell/flutter_gherkin#71) #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tshedor
Copy link
Contributor

@tshedor tshedor commented Jul 26, 2020

This is a rudimentary reporter that reports test results to a Slack channel as they are generated by the driver. Failed steps are reported to Slack with a screenshot. Successful features are reported to Slack with a green checkmark and the number of scenarios that passed within the feature.

Configurable options include terminating after a minimum number of failures and threading test run reports.

(originally jonsamwell/flutter_gherkin#71)

if (step.result.result != StepExecutionResult.pass &&
firstFailedStepInActiveScenario == null) {
firstFailedStepInActiveScenario = step;
for (var attachment in step.attachments) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jonsamwell I added this here to address your feedback. As this repo doesn't access FlutterWorld, it didn't make sense to include the hook that generates the screenshot. I documented it for the implementor's convenience. Do you think that example is sufficient or should it be more visible/cross-documented?

@tshedor tshedor changed the title add Slack reporter (from jonsamwell/flutter_gherkin#72) add Slack reporter (from jonsamwell/flutter_gherkin#71) Jul 26, 2020
@jonsamwell
Copy link
Owner

@tshedor I'm not sure this belongs in the core library tbh. Having a reliance on http might not be viable for some users.

@tshedor
Copy link
Contributor Author

tshedor commented Feb 13, 2021

@jonsamwell I'll leave it up to you. This PR was moved here on your advice from the flutter_gherkin repo. Flutter has http as a dependency, so it made sense there.

If you'd rather close this PR and not be responsible for its maintenance as part of the core, no harm no foul.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants