Your team might consist of a number of expert developers who consistently produce high-quality work, but if they don’t communicate well, your projects will inevitably experience regular hiccups. Prioritizing communication and collaboration is just as important as implementing high-quality standards. Incorporate the tools and suggestions below to create a more open and transparent development workflow and get all of your team members on the same page.
Welcome to the Probo CI Blog!
What is Shift-Left Testing?
You’re likely familiar with the waterfall method of development where testing occurs last or to the far right of the development process. Shift-left testing is a methodology that encourages developers to test earlier and more often.
Baltimore DrupalCamp Recap: Shift Left Testing for Continuous Collaboration
Our CEO, Alex, led a session at Baltimore DrupalCamp 2018 on Shift Left Testing for Continous Collaboration. Shift left testing is the process of moving the testing phase to the left. Usually, testing occurs to the far right in the delivery pipeline which, if you’re moving left to right, is at the end of the development process. However, by testing early and often, you can easily isolate bugs and remedy them faster.
Why You Should Use a Feature Branch Workflow
Talk to a number of different web development teams and you’ll find that they each have unique aspects to their workflows. Whether their process remains consistent or they regularly iterate to optimize efficiency, no team works in exactly the same way.
Regardless of your team’s quirks, using feature branches is a best practice when it comes to web development.
Why Automated Testing For Accessibility Is Not Enough
Automatic testing for accessibility is not enough to ensure that your site is equally accessible to everyone. There are a number of things automatic testing cannot account for, including alt text, online forms, and rich media. A balance of automatic and manual testing is important when designing an accessible site.
Probo Update: The Probo Shell is Live
The Probo team is excited to announce that the Probo Shell is live!
Previously, users could only run and change the code in the probo.yaml files and view the results from the outside.
Now with the Probo Shell, users can connect directly to their build container with SSH, as well as view logs quickly all within the Probo.CI App. This means developers can view or change settings even after the build has completed.
Why Quality Assurance Is So Important
Even if your development team seems to be reliable and efficient, a quality assurance process will ensure that you’re delivering the best product possible.
Challenges to DevOps Implementation
DevOps has grown in popularity over the last few years as companies continue to realize the advantages of unifying development and operations teams. The DevOps methodology aims at improving workflow and productivity by combining the efforts of operations people and developers. When both groups work together to solve problems, they’re able to deliver software features and updates more frequently and reliably.
Probo Updates: GitLab Integration, New mysqlCnfOptions & Varnish YAML Config Options
The Probo team has been busy working on a few updates. Check out what’s new!
Comparison of Pull Request Preview Tools
We compared Probo against other pull request preview tools so that you can learn more about the features of each tool and determine which will work best for your project and your team.