Related Content
Agile and Testing Change Can Come from Leaders at the Bottom, Not the Top Change doesn’t need to be a decree from the top that forces everything else to follow suit. Change can and should start from the bottom, and that happens after you empower your developers and testers and clearly show why things like agile are critical to overall success. |
||
Why DevTestOps Might Be the Next Big Buzzword The hope with any new concept is that it produces better results while removing certain tedious steps that might cause frustration along the way. While DevOps does change the way you test, you cannot forget that testing is still a major layer to your success. |
||
Understanding the True Meaning of Quality Day-to-day testing techniques, strategy, approach, and automation are all things that teams understand and will continue to implement, but how many teams understand the elements of purpose, belonging, transcendence, and storytelling as they apply to software quality? |
||
DevOps Isn’t a Fad, So You Need to Invest Now It’s easy to get wrapped up in the promise of ten-times greater production, shorter development times, smarter testing, and everything surrounding the fresh idea of the day, but when it comes to DevOps, there’s no longer a need for trepidation. DevOps is here to stay. |
||
A Tester’s Guide to Choosing a Programming Language Many testers want to learn a programming language, but how should they decide which one? Justin Rohrman suggests finding an authentic problem to solve and moving from there to determine which language would be best. You can also ask developer coworkers for suggestions and help—take advantage of available resources. |
||
Why the Gig Economy Thrives in the World of DevOps Even if the industry is booming, it’s not easy filling the full-time DevOps roles. Every software team is vying to find the perfect person to come in and establish a culture to promote improved software release cycles, software quality, security, and rapid feedback on product development. But it's not easy. |
||
An Agile Approach to Change Management Many organizations are reluctant to introduce new tools or technologies, or even to update existing ones. The reason is often framed in terms of risk management, but agile teams already have the tools to manage the risk of change: testing and experiments. These approaches together eliminate gaps in risk identification. |
||
Continuous Exploratory Testing: Expanding Critical Testing across the Delivery Cycle Continuous testing entails executing automated tests to obtain rapid feedback on business risks. Where does that leave exploratory testing? Obviously, it doesn’t make sense to repeat the same exploratory tests across and beyond a sprint, but exploratory testing can be a continuous part of each software delivery cycle. |