Related Content
 |
Making Continuous Integration Work for You Many developers learn about using continuous integration to improve their deliverability speed and decrease the amount of effort needed to launch new features. Actually practicing continuous integration, however, is nowhere near as straightforward as it sounds. Here's how to get started in making CI work for you. |
|
 |
How Testers Can Use Docker to Shift Left and Automate Deployments Docker has several advantages over virtual machines: It’s easier to deal with, starts up faster, and requires fewer resources. Using Docker also can give testers more confidence in their releases. Developers use the same environment that will be used in production, which streamlines code delivery and shifts QA left. |
|
 |
Lessons Learned in Testing a UI Test Automation Tool How do you test a tool to be used for automated testing? If a tool executes an automated test that generates keyboard and mouse events to replay user actions, can the test emulate user input and control another instance of the tool to automatically record and play another test? Here's how you test the test tool. |
|
 |
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. |
|
 |
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. |
