Related Content
 |
Building a Culture of Continuous Improvement A culture of continuous improvement means you are open to improving how you build and deliver. You don't accept the status quo; you choose how to work and feel empowered to change it if it no longer makes sense. Kevin Goldsmith gives some ideas for frameworks to adopt in order to move toward this people-first culture. |
|
 |
The Cross-Browser Testing Landscape Is Ready for DevOps While most websites today are responsive, there is a significant growth in progressive web apps that provide cross-platform mobile and web capabilities from within a web app. Add to this maturing practices around agile development and testing and greater adoption of BDD practices, and the landscape is ready for DevOps. |
|
 |
Testing Your DevOps Is Just as Important as Testing Your Software Many DevOps engineers fail to test their automation code in the same way they test the software they deploy. It's crucial for software to have tests, and this should apply to infrastructure-as-code software too, if we plan to change and improve this code with no worries about breaking automation in our DevOps pipeline. |
|
 |
Accelerate Your DevOps Transformation by Focusing on Culture The toughest part of a DevOps transformation is the cultural changes required to make it successful, so to accelerate your transformation, figure out what they are as soon as possible. Explore your company's attitude toward innovation and the tools you have and how you use them, and it will make the change easier. |
|
 |
Why the Burden of Security Should Be Assumed by the Entire Team Quality can be improved over time, and while it’s difficult to change perception, it’s still possible. But poor security can sink your ship before it even leaves the dock. Invest in the security of your application and be sure to spread that responsibility to multiple levels of your software team. |
|
 |
When Buying New Software, Make Sure You're Getting What You Really Need The first step in any significant software procurement is to assure there is a clear definition of the business problem being solved. If you don’t know what you want, you aren’t prepared to negotiate for it, so you'll end up with a system or tool that isn't what you need—and you'll likely be disappointed at delivery. |
|
 |
How to Get Started Automating Your API Tests When designing a test automation strategy, an area that is often overlooked is automating API testing. API test scripts are faster and easier to write than other types of scripts and can be fairly simple tests. An added benefit is that API testing can be included in your continuous integration tools for quick feedback. |
|
 |
Embedding Performance Engineering into Continuous Integration and Delivery In the world of continuous integration and continuous delivery, the importance of ensuring good performance has increased immensely. While functional and unit testing are relatively easier to integrate into these processes, performance engineering has typically raised more challenges. Here's how you can mitigate them. |
