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
We should figure out an efficient way of automatically claim failed tests belonging to the same class and worker.
When py.test worker gets tests assigned, it executes the setupClass fixture on the 1st test. If this one fails, it marks this and all other tests as failure with: "setupClass failed" in the errorDetails. However, only the 1st test contains stdout - thus, the current approach doesn't automatically claim the other tests, if the claiming rule relies on the stdout field.
The text was updated successfully, but these errors were encountered:
We should figure out an efficient way of automatically claim failed tests belonging to the same class and worker.
When py.test worker gets tests assigned, it executes the setupClass fixture on the 1st test. If this one fails, it marks this and all other tests as failure with: "setupClass failed" in the errorDetails. However, only the 1st test contains
stdout
- thus, the current approach doesn't automatically claim the other tests, if the claiming rule relies on thestdout
field.The text was updated successfully, but these errors were encountered: