Probo is a tool that was born of our need to have an easier way to test the web apps that we were creating. It has been open source from the very beginning and as we discovered that it would be helpful to others we have built our SaaS product out of these open source components. We get lots of questions about what features lie in Probo's future and I thought I would share our roadmap here on our blog so that others could comment and make requests.
Yesterday we pushed a big release that gave us a lot of behind the scenes improvements and a few that will be very visible to our users. When you tried to visit a build that we removed because you pushed newer code or because you had exceeded your disk quota, we would serve you an internal error in JSON format. Some of our power users learned to know what those error codes meant but for most people it was disorienting and definitely didn't feel very polished.
To use this process, you are required to maintain your own infrastructure to spin up QA servers quickly, run automated tests and share the testing instance between team members. And preferably, you do it every time an update is applied for any of the modules across your websites.