In our previous articles, we explored the fundamentals of Mockingbird and how to set up your mock server. In this third installment of our Mockingbird series, we delve into one of its most powerful features: Presets. Presets significantly enhance productivity and efficiency when testing and debugging APIs, making them an essential tool for developers and QA teams.

What are Presets?

Presets in Mockingbird are collections of routes with predefined responses. They allow you to quickly switch between different test scenarios by applying a preset, which updates the active responses on all routes within that preset to their specified values.

Benefits of Using Presets

1. Efficient Testing and Debugging: Presets enable you to rapidly switch between different test scenarios without manually changing each route's response. This streamlines the testing and debugging process, saving valuable time and effort.

2. QA Automation and Manual Testing: Presets are particularly useful for QA automation and manual testing. By applying a preset, you can quickly set up the desired test environment, ensuring consistent and reliable testing across different scenarios.

3. Developer Productivity: Developers can leverage presets to efficiently debug specific scenarios without the need to manually modify each route's response. This enhances productivity and allows for quicker issue resolution.

4. Consistent Demos: Presets are invaluable for demonstrating your application's features. By setting up various test scenarios in advance, you can seamlessly switch between them during a demo, providing a polished and professional presentation.

5. Training and Onboarding: Presets can be used to create specific scenarios for training new team members. This ensures that new developers or testers can easily understand and interact with the system without setting up their own test cases.

6. Simulating Edge Cases: Presets allow you to quickly simulate edge cases or rare scenarios that are hard to reproduce in a live environment. This ensures comprehensive testing and robustness of your application.

7. Collaboration Across Teams: Presets can be shared across different teams, ensuring that everyone is testing and developing against the same scenarios. This improves collaboration and reduces discrepancies between environments.

Using Presets in Mockingbird

To use presets in Mockingbird, follow these steps:

• Create a Preset: In the Mockingbird interface, navigate to the "Presets" tab

Click on New folder, fill the folder name and filename and then click save.

Then click "Add Preset".

Give your preset a descriptive name and save.

Click on Add route and then dialog will open and let you select the desired route.

In the dialog select the server parent and the desired route, then you will have a list of all the responses on this route and you will be able to select the desired response, select the response and hit save.

In the preset details you will see the server block and inside it the route parent and under the parent the selected route, on the route row you will see the selected response name.

Repeat this process with all the routes that you want to add to the preset.

• Apply a Preset: Once you have created one or more presets, you can apply them to your mock server. Simply select the desired preset from the list, and Mockingbird will update the active responses on all routes within that preset to their specified values.

• Test and Debug: With the preset applied, you can now test your application against the configured responses, simulating different scenarios without modifying your codebase or waiting for backend changes.

• Switch Between Presets: To test a different scenario, simply apply another preset. Mockingbird will seamlessly update the active responses, allowing you to quickly switch between test environments.

By leveraging the power of presets in Mockingbird, you can significantly streamline your API testing and debugging workflows, enabling faster iterations, improved collaboration, and ultimately, more efficient development cycles.

Upcoming in This Series

• Setting up a GraphQL Mock Server with Mockingbird.
• Managing Multiple Projects and Servers in Mockingbird.
• Dynamically Updating Mockingbird Responses from Automated Tests.

Engage With Us

Follow me on Twitter, also you can join the discussion or share your experiences on our subreddit or directly in the comments below. Your feedback helps us improve and guides our future developments.