-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: new method(s) to check if an object historyState contain a given Status #72
Labels
enhancement
New feature or request
Comments
mrc-mm
pushed a commit
that referenced
this issue
Jul 31, 2023
mrc-mm
pushed a commit
that referenced
this issue
Aug 2, 2023
GTaenzer
added a commit
that referenced
this issue
Aug 2, 2023
GTaenzer
added a commit
that referenced
this issue
Aug 2, 2023
GTaenzer
added a commit
that referenced
this issue
Aug 2, 2023
…en status (#73) * feat: new method to wait that an order has at least reached a given state. (#72) * feat: new methods to wait that a business object has at least reached a given state. (#72) * feat: new methods to wait that a business object has at least reached a given state. (#72) * feat: new methods to wait that a business object has at least reached a given state. (#72) * feat: new methods to wait that a business object has at least reached a given state. (#72) * feat: new methods to wait that a business object has at least reached a given state. (#72) * chore: raise maximum db pool size from 20 to 30(#72) * feat: wait for at least state reached for orders and returns (#72) * feat: wait for at least state reached for orders and returns (#72) --------- Co-authored-by: Marc Mamin <m.mamin@intershop.de> Co-authored-by: Götz Tänzer <G.Taenzer@intershop.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current methods check that a n object has a given state, which might nly be reached after a retry/repair job.
Some test could be faster if we can test that an objec has passed a given state.
AB#88193
The text was updated successfully, but these errors were encountered: