TL;DR
I created a mock tool that can significantly increase your productivity and reduce your integration time to nearly zero.
Mockingbird Homepage.
Mockingbird Releases.
Motivation
In my journey as a developer, I’ve encountered the common challenge of waiting for server development to be completed, which often led to significant delays in our projects.
Frustrated by this inefficiency, I decided to take matters into my own hands and develop a solution.
This led to the creation of Mockingbird, a tool designed to streamline server mocking with an intuitive interface.
Implementing Mockingbird within my team not only reduced our waiting time but also transformed our development process.
With integration times nearly eliminated, our productivity soared.
Now, as I share Mockingbird with the wider developer community, my goal is to provide others with the same opportunity to optimize their workflows and achieve seamless development experiences.
How mockingbird works
Mockingbird works with your Git setup, keeping things simple and secure. No need for extra servers or worrying about security — just focus on coding. With Git being so widely used, Mockingbird fits right into your team’s workflow. Any APIs you add are instantly available to your teammates. It’s an easy, safe way to develop and test APIs without any extra hassle.
Downloading and Installing Mockingbird
- Go to Releases and download the latest stable version of Mockingbird for your operating system.
- Run the installer and follow the on-screen instructions to complete the installation process.
Initializing Your Project in Mockingbird
Locate the Mockingbird application on your system and launch it.
The initial screen is your starting point for creating and managing projects.
Once you opened the app you have two options to start a new project
- Clone existing project of mockingbird from your git service
- Create new project locally (you can connect it to git at any time)
Cloning project from Repository
- Choose between HTTPS or SSH cloning methods. SSH is recommended for its security, but it requires SSH keys to be set up on your system.
- Input Repository URL:
- For SSH: Enter the SSH URL into the ‘ssh url’ input field.
- For HTTPS: Switch to the HTTPS tab and enter the repository URL into the provided field.
- Type in a unique name for your project in the ‘project name’ input field.
- Click the ‘CLONE’ button to clone the repository and establish your project in Mockingbird.
Setting Up Your Project
Initiating a New Server
- Click on the
+ new server
button - A dialogue box will appear, insert your server name.
- Hit
SAVE
.
Creating parent
- Adding a new parent, parent will hold the routes under it
- select
New Parent
- insert the parent path in the
path
field - insert filename in the
filename
field, this will create new file in your project that will hold all the routes in it
Creating route
- Select
Add Route
. - Specify the HTTP method and route path.
- You can ignore the params row.
- Click
ADD ROUTE
to add the route to your server.
Adding Response
- Once your route is created, select your route
- click on
ADD RESPONSE
button. - You can choose between three response options
function
object
andproxy
-
Function
will give you the option to create custom response based on params you have on your request. -
Object
will return the object that you set to response. -
Proxy
will pass your request to a url that you set. - Choose your response type and fill the data, set response name and hit
SAVE
.
You can add multiple responses and switch between them by clicking on SET ACTIVE button.
Spread the wings!
Now that your all set, hit the start server
button, and your mock server is up and running.
In the top bar you will have servers ips
button, hit it and you will see your server address.
Open the console to view all the requests handled by the Mockingbird server.
To start mocking, simply change the baseUrl
in your project so all your API calls will directed to your mockingbird server.
In Conclusion
Mockingbird is a powerful tool that can help not only front-end developers, but also can help back-end developers that need to integrate with 3rd party services, it can help QA that needs to have a specific environment for their testing, also Automation that needs its own servers, and you can take it further,
I hope that you will find use out of it and enjoy it.
Even if you don't plan on using it, I would still be grateful if you could endorse and star it on Github.
In the next articles:
- Setting up a Full Mock Server for Your APIs in minutes.
- Setting up GraphQL Mock Server with Mockingbird.
- Mockingbird: The power of Presets.
- Manage Multiple Projects in Mockingbird.
- Manage Multiple Servers in your Mockingbird project.
- Mockingbird console, quick overview.
You are more then welcome to ask questions and leave comments or raise an issue in the Github issues page.
Happy mocking, fellow developers!
Top comments (8)
Hi @ozkeisar
I recently discovered your application for mocking server data, and I wanted to take a moment to express my appreciation. The functionality is incredibly intuitive and has been a game-changer for my development process. Your attention to detail and the user-friendly interface make it a pleasure to use. Thank you for creating such a valuable tool for developers!
Thank! I'm glad to hear
Great app, what is this app built with .. is source available for customisation?
Thank! It's built with react electron
You can give a feature suggestions and I'll try to add them!
Hi, great!
Can you describe, why you can't use the wiremock.org/ ?
Did you research alternatives?
I agree that it looks similar,
But there is a differences
For instance my tool is designed to work over git (for security and simplicity ),
In Mockingbird you can create several servers and simulate numerous of environments,
Also I developed Presets and I will write about it in the future posts,
And one more Mockingbird is a app not a package.
and mockoon.com
I experimented with Mockoon, but it lacks many of the features I require.