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

Feature request: Pass/fail reporting #240

Open
ablwr opened this issue May 16, 2017 · 2 comments
Open

Feature request: Pass/fail reporting #240

ablwr opened this issue May 16, 2017 · 2 comments
Assignees
Milestone

Comments

@ablwr
Copy link
Contributor

ablwr commented May 16, 2017

Users would like a high-level overview of groups of files that determine whether something has failed and which files have failed. Dashboard should reveal all files that are failing. Should also be able to click thru to identify further. “Your thing failed, go look at it!”

@kgrons
Copy link

kgrons commented May 19, 2017

Use Case: user opens SignalServer daily(?) following automated tests. Dashboard summarizes failures for manual investigation + remediation.

Functional:

  • test date, thresholds failed, list of files failed per threshold per date, ability to navigate to problem files in QCTools environment (direct link or some type of path?)

UI:
Could be specified further by collapsed summary starting with test date and clicking to open lists individual failures and files:
-[Date of test]
-+ FAILED | [summary of failed threshold]
-- FAILED | [summary of failed threshold]
---file [click to open in QCTools or click thru for source file path or something]

Possible improvement: Ability to export the summary and details (CSV?), e.g., for long term deck monitoring and/or collection/batch-level stats.

@ablwr
Copy link
Contributor Author

ablwr commented May 19, 2017

Thanks so much @kgrons 🎉

@yayoiukai yayoiukai self-assigned this Jul 2, 2017
@ablwr ablwr added this to the 0.2.0 milestone Jul 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants