Omnis Studio lets you create amazing solutions for any platform quickly. Since a programmers work is never done; enhancements are inevitable followed by another deployment cycle.
Programming is definitely the fun part. The DevOps approach minimizes the time and effort extensively testing changes and wrapping up your new feature before deploying it to customers. A little effort building your DevOps infrastructure automates your build, testing and deployment phases of the application development lifecycle and gives you back time to focus on your next feature.
Studio’s built in export library to JSON is the key. Git is the ideal companion tool (which is very very widely used in all languages) and provides a distributed code repository (replacing the VCS). It supports feature branching, rollbacks, code compare and identification of who/ made changes and when to specific lines of code in a class or method. If OmnisTAP (automated testing) is implemented as part of the build process, the additional benefit is ongoing regression testing of the impact of your changes. The final stage may be a build to a deployment tool of your choice.
DevOps tools like Jenkins or Gitlab run your scripts incorporating the chosen parts (above). Simply check your code in, and these tools report successful tests, those that failed & why, and, if they all pass, it can build a deployable application or payload to your Omnis server as the need may be.
Whether you’re seasoned using unit testing and continuous delivery with other products or completely new to these concepts, this class is for you. We will cover:
Most of us already do all these tasks in some form or another. Automation takes best practices to a new level for Omnis Studio and gives you time back!
This session builds upon the Introduction to OmnisTAP (above); by focusing on unit and integration testing, particularly testing of legacy code.
Learn how to update large, “spaghetti code” methods to be unit-testable and how test-driven development helps direct your new code in a clean, quality direction. Bring your current libraries, your questions and we’ll explore the world of testable code. Topics include:
It is recommend that you attend the DevOps session first or that have some prior experience with a testing framework.