How To And Why You Should Use Probo

Don’t merge code that breaks the build.
Every Project Lead, Everywhere

This has long been the mantra of the Probo.CI team. Developer testing, unit testing and regression testing are critical parts of the software development life cycle.

Probo.CI helps break down the barriers inherent in a software development project. It works with git on a per-pull-request or commit basis to ensure that you never merge code into any branch before it has been tested and approved.

Probo.CI was initially created to fulfill an internal need for automated testing of Drupal and other database driven web applications, which popular continuous integration tools like CircleCI and Travis couldn’t fill. Once the tool started to take shape, we realized that we had created a something that did more than just make automated testing better; by giving a very granular real-time view into the state of development before the work was merged into a git branch, it seriously improved the lives of project managers, product owners and clients, quality assurance and user acceptance testing staff, and junior developers.

The Probo.CI workflow recognizes that there’s more to deploying development work than automated testing. Real people will always need a place to see, test, and approve changes. By factoring in real human testing and approval processes into the development to deployment process, we can improve quality, efficiency, and collaboration.

Today, Proboi.CI is owned and operated by FlyingFlip Studios, LLC with the goal of providing a testing platform for as many web technologies as possible with an eye toward allowing visual, functional, and unit testing to be conducted in a way where development issues can be caught early and resolved before they get in front of your production environments and your end users.