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
{{ message }}
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
My request in question has five tests: one test to make sure the status is 200 and four tests that run inside the specFunction, so they only run when the response is otherwise marked as successful.
The third test was updating an environment variable and the test would exit on that update. Everything in the request after that line wouldn't report test results in the Test Summary. It seemed like updating the environment variable was throwing an exception.
Encapsulating the environment lines with a try/catch doesn't seem to yield anything either; it still exits early.
The tests run as expected when manually running the request, but when the flow hits it, I'm missing the last two test results.
This is critical for me. It means I can't rely on it to accurately report on my tests until this is fixed.
I love the flows and think they have incredible potential, especially when I need to test user flows through multiple APIs, but the test summary needs to accurately report the tests it runs. Once that's fixed, I also think it would be really helpful to have a number to reference for passed/total tests, e.g. 18/19 tests passed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
My request in question has five tests: one test to make sure the status is 200 and four tests that run inside the
specFunction
, so they only run when the response is otherwise marked as successful.The third test was updating an environment variable and the test would exit on that update. Everything in the request after that line wouldn't report test results in the Test Summary. It seemed like updating the environment variable was throwing an exception.
Encapsulating the environment lines with a try/catch doesn't seem to yield anything either; it still exits early.
The tests run as expected when manually running the request, but when the flow hits it, I'm missing the last two test results.
This is critical for me. It means I can't rely on it to accurately report on my tests until this is fixed.
I love the flows and think they have incredible potential, especially when I need to test user flows through multiple APIs, but the test summary needs to accurately report the tests it runs. Once that's fixed, I also think it would be really helpful to have a number to reference for passed/total tests, e.g.
18/19 tests passed
.Beta Was this translation helpful? Give feedback.
All reactions