As features are completed, they are pushed into the release candidate branch for testing. At this point, we will also create automated tests that run as part of the pipeline. Tests are useful for testing the new functionality or ensuring we are not breaking functionality for historical changes we have made before (this is called regression testing).
Sometimes, if the work is reasonably complex, what we call a pull request is created so that other developers on the team can review the code before approval. During or immediately following
development, the work item is handed over to our QA (Quality Assurance) team to test the new functionality (or bugfix) and to update Clever Documentation online.
Finally, once the development is complete, tested and documented we generate translations and push the work back into the master branch. The DevOps pipelines run automatically, every single automated test must run successfully, and a completed build of the new version is uploaded to Clever Drive (For our on-premise installations of Dynamics 365 Business Central). The QA team also ensure that the new version is delivered to Microsoft AppSource, the online marketplace where you can find all of our products.
Phew! Sounds like a lot? Well, we’re used to it and DevOps takes a huge amount of the strain. Our goal is to provide useful and usable software of the highest quality we can muster.
If you have an idea that will make you and your customer's lives easier, let us know. Contact us through our website, email at