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.
Not really a problem, more an inconvenience. If I wanted to write a test to wait that a certain timer has been fired twice, currently this would mean:
await-element-instance-state - activated
await-element-instance-state - completed
await-element-instance-state - activated
await-element-instance-state - completed
This makes it difficult to understand the intention of the test.
A shorthand action could be introduced to first wait for one state, than another state. The shorthand could also check that the transition makes sense (e.g. activated to completed makes more sense then completed to activated)
Describe the solution you'd like
I'd like to have an action with the following spec:
- action: await-element-instance-state-transition
args:
element_name: B
from-state: activated
to-state: completed
Additional context
Not sure how relevant this will be for the tests, but this could also be a place to specify for the test to wait for the n-th state transition.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Not really a problem, more an inconvenience. If I wanted to write a test to wait that a certain timer has been fired twice, currently this would mean:
await-element-instance-state - activated
await-element-instance-state - completed
await-element-instance-state - activated
await-element-instance-state - completed
This makes it difficult to understand the intention of the test.
A shorthand action could be introduced to first wait for one state, than another state. The shorthand could also check that the transition makes sense (e.g. activated to completed makes more sense then completed to activated)
Describe the solution you'd like
I'd like to have an action with the following spec:
Additional context
Not sure how relevant this will be for the tests, but this could also be a place to specify for the test to wait for the n-th state transition.
The text was updated successfully, but these errors were encountered: