Related Content
 |
Protect Your Software through Threat Modeling Many software organizations are overwhelmed with a laundry list of vulnerabilities. They often have no idea where to start, how to determine prioritization, and whether or not those vulnerabilities accurately represent the threats to our applications, users, and data. Threat modeling is a simple yet effective solution. |
|
 |
FDA’s New Digital Health Report To update health care providers, patients, and developers about some of the risks and benefits surrounding software products, the FDA released a report based on impact to patient safety, health benefits and risks, and best practices. |
|
 |
Testing the Ethics of AI AI is a double-edged sword. When it's being used in situations involving sensitive personal data, such as health care, banking and finance, and real estate, security is of the utmost importance—and so are ethical implications. It’s up to testers to mitigate risks and make sure AI is used responsibly. |
|
 |
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. |
|
 |
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. |
