As the Agile environment has efficient principles that allow quick responses to changes and the ability to deal with uncertainty, exploratory testing may seem like a perfect match for such projects. However, this is only partially true. In reality, diverse reasons impede its usage in Agile projects, and companies should take them into account before designing QA strategies.
As software products and services are becoming more complex, it requires more comprehensive testing for identifying the defects and pursuing the necessary fixes before it becomes available for public release. The QA process needs to be planned out and monitored so that it can be successful. The most effective way to track the efficacy of QA activities is to use well-thought-through metrics.
The concept for development teams in a scrum environment is to be self-organizing, basically managing themselves and holding each other accountable. This poses the question: What do QA managers do with their time? For me, it’s always been about building the right culture—respecting those under you just as much as you respect those above you. It is about finding a way to manage your team without being directly involved with them.
When author Zane Roett began a new Senior Manager test role in a new organization in 2019, he found that it became an important task to create and lead the development of a software test engineering professional community of practice (TCoP).
QA testers often take on more of a role than just testing software code. When the team needs help, QA should lend a hand in assisting with business analysis, customer communication, user experience, and user advocacy.
As if working at Lego isn’t fun enough, Sherri Sobanski delights in finding new ways to test. Faced with a situation requiring a complete product redesign, she shares the route her team took to overhaul testing.
QA is often considered that lonely department of testers whose job is to find defects before the customer does. It's not always glamorous, but QA deserves to be recognized as a key cog in the testing machine. To achieve business goals, it is Susan Bradley's view that the QA process needs to be embraced throughout the entire software development lifecycle.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
Dan McFall, president and CEO at Mobile Labs, chats with TechWell community manager Owen Gotimer about trends in enterprise mobility, the role DevOps and the cloud play in mobile application testing, and the transition to working from home.
Davar Ardalan, founder and storyteller-in-chief of IVOW, talks about how her experience working at NPR helped her launch an AI and storytelling startup. She also discusses how testers, QA analysts, and software engineers are on the front lines of working with users and understanding user engagement, and she explains the importance of finding ways to collaborate with them.
Greg Paskal, test automation lead at Ramsey Solutions, talks about data lakes and how to effectively use data visualization. Done well, data visualization should help practitioners, managers, and stakeholders easily consume, understand, and act on the information the visual displays.
Are you a leader with a quality problem? Every organization struggles with quality at some point in their product lifecycle. Knowing what to measure and how to build a culture of quality with specific and actionable methods is key.
Too often quality is identified as solely owned by the quality assurance team. By taking a broader approach to roles, tools, and ideology, you can restructure your vision of how to provide rapid, frequent releases that empower all delivery team members.
Modern software development organizations often build teams around features. Unfortunately, these teams tend to become siloed, building tools and processes without being aware of how other teams have solved the same problems.