📄️ Understanding a Test Case
A test case in PostQode represents a sequence of API requests with defined validations and expected responses. It serves as a blueprint for testing the API functionality, containing all the necessary components, such as request parameters, headers, authentication details, and assertions to verify that the API correctly behaves.
📄️ Creating Test Cases in PostQode
Users can directly create the test cases within the workspace environment and the TestSuites.
📄️ Test Case Dependencies
PostQode lets you define dependencies between test cases, ensuring that tests run in the correct order and only execute if their prerequisites pass.
🗃️ Requests
6 items
📄️ Datasets
Datasets are a powerful feature that enable the data-driven testing by executing the test cases with multiple sets of test data. They provide flexibility for creating the environment-specific datasets and they support to import the test data from the CSV files, which makes the test automation more efficient and maintainable.
📄️ Draft Test Cases
When a test case is created within a test suite, it is initially set to the draft mode, indicated by an orange icon. Any changes made to the draft test case will not be visible to any other user. Similarly, any modifications made to the test suite or the requests within them will place the entire test suite in the draft mode, which is also indicated by the orange icon.
📄️ Hooks
Hooks in PostQode are powerful features that allow you to execute the specific API calls at certain points during the testing process. By using hooks, you can enhance the flexibility and efficiency of your test suites, which makes it easier to set up, prepare, clean up, and tear down the testing environment.
📄️ Assertions
Assertions in API testing are critical for ensuring the quality, reliability, and correctness of APIs. They help users by validating whether the API responses meet expected criteria. Here’s how they help: