Related Content
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. |
||
Continuous Testing Is Not Automation Many people confuse continuous testing with test automation. That makes sense, because you cannot do continuous testing without automated tests. But it is much more. Continuous testing has a higher-level maturity that could require a totally different way of working—but it also gives a faster path to production. |
||
The New Reality of Mixed Reality Want to play with a porg? Walk on Mars? Or help those with autism practice social skills? Welcome to the new reality of mixed reality, where digital and physical objects coexist and interact to provide a new medium that a variety of organizations see as full of potential. |
||
4 Lessons from the STARWEST 2018 Keynote Presentations With a week full of sessions, tutorials, training classes, and events, the STARWEST software testing conference had plenty of takeaways useful for your professional and personal life. Here are four lessons distilled from the conference’s keynote presentations on testing, communication, and directing your career. |
||
Writing Tests: Action Abstraction Keywords have become a popular way of writing tests. Hans Buwalda used keywords to devise the Action Based Testing method in which tests are written as sequences of “actions” represented with keywords. However, keywords are just a physical representation of actions, and there are other ways to do this. |
||
An Exploration of Exploratory Testing Exploratory testing is one of the most widely known but poorly understood practices in the software testing community. The term suggests that exploratory testing is a special testing activity, but in reality, all true testing is exploratory in nature. Let's rediscover what exploratory testing should—and shouldn't—mean. |
||
A Tester’s Role in Requirements Exploration Agile is supposed to get people to talk to each other in real time. However, many teams still lack a shared understanding of what they are going to build, even as they start coding. As testers, we can explore feature specifications early, contributing to successful and timely delivery through defined requirements. |
||
Guaranteed Methods to Ruin Your Test Automation After working to develop the test automation patterns used by experienced practitioners to solve common test automation issues, Seretta Gamba started to consider what can ruin a test automation effort instead. Here she shares two sure-fire methods that can destroy your test automation. Steer clear of these examples! |