Скачать или смотреть How to Check If a Status Code is 200 or 202 in Robot Framework

Learn how to effectively check for `200` or `202` status codes in Robot Framework using conditional logic. Avoid common pitfalls that lead to errors in your testing scripts.
---
This video is based on the question https://stackoverflow.com/q/62407387/ asked by the user 'Mia' ( https://stackoverflow.com/u/11867978/ ) and on the answer https://stackoverflow.com/a/62413093/ provided by the user 'Todor Minakov' ( https://stackoverflow.com/u/3446126/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Check status code is 200 or 202 in robot framework

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Check If a Status Code is 200 or 202 in Robot Framework

In the world of automated testing with Robot Framework, one common requirement for API testing is to verify the status codes returned from API calls. It's particularly important when issuing POST requests, as ensuring the correct response is critical for application functionality. In this guide, we’ll explore how to check if the status code is either 200 (OK) or 202 (Accepted) and troubleshoot an error that often occurs in the process.

Understanding the Problem

When writing a test case in Robot Framework, you might want to check the HTTP status code returned from an API. If you are specifically dealing with POST requests, it's common to expect either 200 or 202. The initial solution you might consider could look something like this:

[[See Video to Reveal this Text or Code Snippet]]

However, this approach is flawed. Attempting to check for multiple values in this manner will lead to errors, such as:

[[See Video to Reveal this Text or Code Snippet]]

The Solution: Two-Step Verification

The crux of the issue lies in the way the RequestsChecker.Check Response Status keyword is designed. This keyword only accepts a single response code, and it expects that code to be an integer. You cannot pass multiple values using logical operators like || or or in this context. Instead, you can check each expected status code separately.

Step 1: Separate Checks for Each Expected Code

Use the following code to check for the status codes 200 and 202. The test will run two separate checks, each validating one response code:

[[See Video to Reveal this Text or Code Snippet]]

Run keyword if: This command allows you to conditionally run a keyword based on some criteria. Here, it checks if the method is POST.

Run Keyword And Return Status: This variant allows us to capture the success (or failure) of the keyword into a variable.

Step 2: Fail Gracefully if Neither Condition is Met

After checking both statuses, you need a way to handle scenarios where the response does not match either of the expected codes. To do this, you can include a failure condition:

[[See Video to Reveal this Text or Code Snippet]]

Fail: This keyword allows you to explicitly fail your test with a specified message if the condition is not met.

Conclusion

By breaking down the checking of status codes into two separate invocations and handling potential failures neatly, you will create a more robust testing script in Robot Framework. This method not only prevents errors from arising but also provides clearer test results for API responses.

Implement these techniques in your automated API tests to ensure your HTTP response validation is both effective and error-free!