Related Content
The Key Areas Where Testers Need to Grow With new methodologies, technologies, and innovations constantly being introduced, testers need to continue to push forward with an open mind and an understanding of different disciplines to make sure they have a rock-solid standing in the process. |
||
How to Communicate to Build Trust on a Scrum Team Trust among the ScrumMaster, product owner, and development team is essential to making the process work. Transparency, inspection, and adaptation are the three pillars of Scrum, and you can't commit to these actions if everyone doesn’t have openness and respect for each other. Communication is the best way to do that. |
||
3 Core DevOps Values for Testers to Know With DevOps, modern software teams of all shapes and sizes are aiming to deliver a high-quality software production early and often. Shifting testing earlier into your development lifecycle and smartly using test automation to reduce bottlenecks can create a more seamless, collaborative business. |
||
The Debate over Testing versus Checking Testing and checking, like a lot of language in software testing, is there in order to more precisely describe something we are already doing. However, there is a strange plague of people who feel the need to police others' language whenever they try to use the terms interchangeably. What we need is more understanding. |
||
Keeping Your Software Testing Abilities Relevant Today, Tomorrow, and Beyond Development and product teams have embraced agile and DevOps. What can testers do to keep up with their development peers? Here are some ideas about what testers can learn, what skills we can add, and what processes we can start doing in order to continue delivering quality today, tomorrow, and further into the future. |
||
Software Testing and Development Is Now a Team Sport One person might be the spark that starts the fire, but it takes multiple people to help keep the flame burning. Developers and testers rely on each other more and more these days, and you need to be able to pass something along to someone with different talents in order to successfully reach the finish line. |
||
Choose Continuous Integration over Branching for Faster Feedback Continuous integration is the best way to get feedback often on the state of your project. Running automated builds and tests after each integration improves reliability and predictability. Consequently, using task and feature branches, while useful in some cases, can be a distraction and delay getting information. |
||
Make Your Security Testing More Agile Security practices traditionally have followed a waterfall model, adding security testing on at the end. Organizations need to coach their security programs and testers to prioritize analysis and risk, much like we do with agile stories, to better incorporate security defects with other feature work along the way. |