-
Notifications
You must be signed in to change notification settings - Fork 2
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
[api-tests]: Test-Scripts expect different test results #18
Comments
Here is some additional information to how I ran the tests. Command: The output is always the same: Test-Script Command Output
|
@TobyTheHutt we are currently facing the same problems. We are trying to figure out how these tests were supposed to be executed. |
Describe the bug
I encountered an issue while running the provided Python script
api_tests.py
. I tried to run it both with the provided Shell-scripts and by its own. The script reports an AssertionError with the following message:AssertionError: Did not get expected completion states [<TransactionStates.FAILED: 3>] but TransactionStates.NEW after 32 retries.
Version of Python and LGS:
What happened:
The script is designed to monitor API transactions and wait for them to reach certain completion states. However, the script is raising an assertion error with the mentioned message, indicating that the expected completion state of
TransactionStates.FAILED
was not reached within the specified number of retries.I ran the scripts on the same host and the same Docker network on which LGS is running. I can reproduce this behaviour in both our corporate server infrastructure as well as on my local machine.
What you expected to happen:
I expected the script to successfully wait for the transaction to reach the expected
TransactionStates.FAILED
state.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
I have reviewed the script, and the configurations, enumerations, and logic appear to be correct. The issue seems to be related to the API's behaviour or timing.
The text was updated successfully, but these errors were encountered: