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. |
||
Up Your Security: Turn On Two-Factor Authentication You may think that if you always take care not to share personal information online and regularly update security settings, turning on two-factor authentication is an unnecessary step. But the truth is there is always a risk. Let's look into how two-factor authentication keeps your personal information more secure. |
||
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. |
||
Is It Time to Stand Up for the Web? Does the Web need fixing? Widely acknowledged as the creator of the World Wide Web back in 1994 and the current Director of the World Wide Web Consortium on web standards, Tim Berners-Lee launched #ForTheWeb to help resolve what the organization views as current risks and future challenges. |
||
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. |
||
Making Testing Visible Most testing work is invisible—something that happens inside your head and leaves no artifacts behind. This generally leaves testers feeling like no one understands what they do all day. Here are some ideas for collaborating with your coworkers so they can see—and start to understand—your testing work. |