You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: