Section Wrap Up | Bondar Academy

Lesson Summary

This section wraps up the discussion on schema validation versus regular assertions in API testing. When to Use Schema Validation Use schema validation after every single response. This method is straightforward and helps ensure that your API does not have integration issues. You can recreate the schema and run the schema test repeatedly. When to Use Assertions Use assertions when you want to validate specific properties that were modified during the test. For example, in the test for creating and deleting an article, you should: Use schema validation for the overall response. Use assertions only for the properties you changed, such as title , description , and body . There is no need to validate properties that were not impacted by your test, such as the date, author, or favorites. The schema validation will cover those aspects. General Rule If your test involves a functional operation and you made changes, validate the result of that action. For all other properties, rely on schema validation, which is typically sufficient. In summary, use schema validation for comprehensive checks and assertions for specific changes made during tests. This approach will streamline your testing process.