At Woovi, we focus in to deliver the best cost x benefit for new features. And, with our core principles in mind, even before coding, we start to sharpen the best solution for our clients.
Let's give into our Testing and Release process.
Testing process
To understand our development process, you must first know how our environment operates.
We dispose of two environments: staging and production.
Staging
Staging is our testing environment. All pull requests from our developers go to the staging environment directly if they pass all tests.
The staging helps us test our product features.
This approach is close to the based trunk development.
In addition to automated testing, we also emphasize the need for testing how our customers will perform. You could write many tests as you can. But, when running in the browser, there is a probability that you can find a bug that the automated test didn't catch it.
When the developer ship the feature to staging we create a test plan for. We have a blog post dedicated to this. You can read more here Test Plan Driven Development
Release
All tests are performed, changes reviewed, and the next step is to go forward with our release.
We automated our release by creating a slack bot that brings all changes comparing the last release and generating a diff to us.
Then, with one click only, we disparate our release.
If you like this blog post, come to work with us, we are hiring!
Woovi
Woovi is a Startup that enables shoppers to pay as they like. To make this possible, Woovi provides instant payment solutions for merchants to accept orders.
Top comments (0)