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

Your Use Cases are important! #113

Open
PurHur opened this issue Jul 5, 2019 · 1 comment
Open

Your Use Cases are important! #113

PurHur opened this issue Jul 5, 2019 · 1 comment

Comments

@PurHur
Copy link
Collaborator

PurHur commented Jul 5, 2019

Hey,

lets discuss some usecases of this plugin/report. We should collect some data about our usecases and what we need in the very basic base template. (This can be switched soon)

I have a few questions but dont bother so explain what and why something is important for you in the report.

How many tests do you have in one report?
How much are failing if something happen?
How do you organize your tests? folder structure? tags?
Do you store each report? How big should it be?
Parallel stuff?
Do you send them via email?
Do you use this as a dashboard?

Would be great to see some input here to move forward.

@donkidd donkidd changed the title Your Usecases are important! Your Use Cases are important! Jul 5, 2019
@fr33ek
Copy link

fr33ek commented Jul 17, 2019

Hello!

I have about 400 scenarios.
Sometimes it can fail about 100.
I just have folder tests/behat.
I save reports as an artifact for some time only if pipeline failed. I use gitlab-ci for this.
I run two test jobs in a parallel, they have different reports.
I don't send them vie email for now, and don't use on a dashboard.
I still have some problems showing screenshots in my report - that is needed feature for me.

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

No branches or pull requests

2 participants