Related Content
 |
Can We Ever Find All Bugs? This may not be what testers want to hear, but Ingo Philipp is convinced we can't ever answer the question "Did we find all bugs?" It all comes back to the fact that testing can prove the presence of bugs, but not their absence. Here, Ingo explores how we find and fix bugs, as well as the notion of quality assurance. |
|
 |
Who Should Be Doing Automation Work? Testers often look at automation work as the next career step after manual testing. Automation work has more visibility at the project level, and people who do this work usually also tend to have a little more social status. But Justin Rohrman makes a case for why testers shouldn't be the ones doing automation work. |
|
 |
Agile Collaboration on Remote Teams The first value in the Agile Manifesto is “Individuals and interactions over processes and tools,” and for many teams, being located in the same place facilitates these interactions. However, being part of an effective, collaborative team is less about location than it is about motivation and good practices. |
|
 |
What to Keep in Mind If You Want to Be Persuasive To successfully persuade someone of something, it’s important to keep in mind how you come across to others—when you’re trying to persuade and when you’re not. It's a good idea to build up trust and credibility before you need something, listen to others when they're in need, and think about tailoring your message. |
|
 |
5 Reasons You Should Have More Unit Tests The test pyramid is a valuable visual in agile. In particular, it argues that unit tests should make up the majority of tests, and while agile teams recite this principle, it is often not clear why it is so important. Here are five reasons unit tests should make up the majority of tests written for an application. |
|
 |
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. |
|
 |
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. |
|
 |
Creating a Cohesive Culture in a Distributed Organization When organizations are distributed across multiple locations, it brings questions about how much each location should have a unique identity relative to the larger company. While a theme of “we are one” is common, it’s better to embrace the differences and work toward being a cohesive group that celebrates diversity. |
