quality assurance

Evangelist holding up a light bulb What It Means to Be an Evangelist for Quality

The role of evangelist is often not very well known—or even if it is, it is not well understood in terms of its differentiation from closely associated functions, such as sales and marketing. But when understood and implemented well, it is a very powerful role. What does evangelism mean in terms of software quality?

Rajini  Padmanaban's picture
Rajini Padmanaban
Shift key on a computer keyboard Making the Switch from Quality Assurance to Quality Engineering

The quality engineering approach differs from QA in that quality teams partner with business users and product managers to better understand requirements and to catch problems as products are being built—not after the fact. There are two pillars to building a true quality engineering organization: culture and process.

Sumeet Mandloi's picture
Sumeet Mandloi
Developer writing code at his computer The Developer’s Role in Testing and Quality

Of course a developer's primary job is to produce good code, but there's also a lot they can do to contribute to quality and test their code before it gets to a tester. Code quality techniques help developers write better code, more thoroughly understand their changes, and avoid builds with many easy-to-find problems.

Justin Rohrman's picture
Justin Rohrman
Neon sign with an open mind Open-Mindedness Is Revolutionizing Quality Engineering

The most important element for revolutionizing quality engineering across the board—for testers, others in the product group, stakeholders, and even competitors—is an open mind toward quality. This means a willingness to consider new avenues toward pursuing quality, including techniques, roles, and attitudes.

Mukesh Sharma's picture
Mukesh Sharma
View from above of five coworkers fist-bumping over their computers 4 Ways to Increase Software Quality and Decrease Test Time

Software testers are continually under pressure to test faster without sacrificing quality. By taking the perspective that quality is the responsibility of the entire team, not just the testers, shorter test cycles with higher quality software are possible. Here are four ways the whole team can improve releases.

Richard Estra's picture
Richard Estra
Image of a person's face made out of code Designing a Smart QA Strategy

With increasingly complex and sophisticated technologies being used in testing, quality has to become a smart activity. A smart QA strategy is both about building smart models and making smart choices. We must keep in mind the balance between manual and automated solutions and which are needed to accomplish our goals.

Mukesh Sharma's picture
Mukesh Sharma
Hand holding a camera lens focusing on faraway mountains Agile and DevOps Bring the Focus Back on Quality

As companies move to agile and DevOps, silos are coming down and there is more interaction and collaboration among teams. Quality is also becoming everyone's responsibility for the entire software development lifecycle. Quality is more than just testing: Consider a quality value stream along the overall value chain.

Michael Sowers's picture
Michael Sowers
Microphone on a stage at a conference Lessons Learned (and Unlearned) at STARCANADA 2018

With a week full of sessions, tutorials, training classes, and events, the STARCANADA software testing conference had plenty of takeaways. Some highlights: what jobs will look like in the future with AI, why testers should lead efforts to make quality everyone's responsibility, and the importance of unlearning.

Owen Gotimer's picture
Owen Gotimer