search

mobile-dev-inc / maestro

Painless Mobile UI Automation
https://maestro.mobile.dev/
Apache License 2.0
5.67k stars 257 forks source link

[Feature Request] Add the ability to configure different email for different individual/bunch of tests #1925

Closed mrinalkhanvilkardd closed 1 week ago

mrinalkhanvilkardd commented 3 weeks ago

Is your feature request related to a problem? Please describe. Currently whenever a test fails there is a way to email for the overall test suite failure to a single email. We are multiple team writing maestro tests cases for our individual features. With just email, it creates a lot of noise. It would be great if we would be able to configure email for individual/bunch (folder) of tests.

Describe the solution you'd like Along with the config.yaml at the root, it would be preferable to have a config.yml for individual subfolders. Another solution is to add an overriding email address (or slack channel) in the test itself.

Describe alternatives you've considered Currently we have to manually take a look at the dev console and we are trying to prevent that

Additional context

bartekpacia commented 3 weeks ago

Hey @mrinalkhanvilkardd – thanks for this suggestion.

Would a webhook work for you? I.e. you'd receive a webhook from Maestro Cloud whenever a test suite completes, and in the payload you'd have data about specific flows, etc. Then you could apply filtering yourself, and we'd avoid adding more complex code to Maestro. How does that sound to you?

mrinalkhanvilkardd commented 3 weeks ago

Hey @mrinalkhanvilkardd – thanks for this suggestion.

Would a webhook work for you? I.e. you'd receive a webhook from Maestro Cloud whenever a test suite completes, and in the payload you'd have data about specific flows, etc. Then you could apply filtering yourself, and we'd avoid adding more complex code to Maestro. How does that sound to you?

Hi @bartekpacia our current CI is bitrise, let me check if that would work with that.

bartekpacia commented 3 weeks ago

I used Bitrise; it allows you to execute arbitrary code, so you should be able to collect results yourself, and do whatever you want with them.

github-actions[bot] commented 1 week ago

Without additional information, we can't resolve this issue. We're therefore reluctantly going to close it.

Feel free to open a new issue with all the required information provided, including a minimal, reproducible sample. When creating a new issue, please make sure to diligently fill out the issue template.

Thank you for your contribution to our open-source community!

github-actions[bot] commented 4 days ago

This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. Thank you for helping keep us our issue tracker clean!