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

Categorize alarms by type of failing step, not test case #343

Open
SleepyLeslie opened this issue Mar 7, 2024 · 3 comments
Open

Categorize alarms by type of failing step, not test case #343

SleepyLeslie opened this issue Mar 7, 2024 · 3 comments

Comments

@SleepyLeslie
Copy link
Member

Is your feature request related to a problem? Please describe.
Acto could fail prematurely when an error occurs before it reaches the final step of a test case. However, Acto reports the type of the test case in the alarm, not the failing step. This makes the alarm information confusing.

Describe the solution you'd like
Acto should report the type of the failing step. For example, if a test case intends to test object deletion but the step that creates the object first fails, Acto should report "object-creation" in the alarm, not "object-deletion".

Describe alternatives you've considered
I just ignore the test case info and directly look at the logs to figure out what has happened, but it's always nice to have an accurate overview before diving into the details.

@tianyin
Copy link
Member

tianyin commented Mar 7, 2024

Would you be able to help fix the bug? @SleepyLeslie :)

@SleepyLeslie
Copy link
Member Author

This is a desired new feature rather than a bug. I have contacted @tylergu for some guidance on how to start looking into it, and will attempt to implement it when I have time.

@tianyin
Copy link
Member

tianyin commented Mar 12, 2024

thanks for clarifying it (and you did last Friday).

no pressure if you don't have time, especially that you already planned something else for the course project.

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