Related Content
Top 10 TechWell Insights Stories of 2018 Many teams are embracing new practices, and several of last year's most-read stories reflect that, with topics such as AI, DevOps, and continuous testing. But it looks like lots of teams also want to get back to basics, because guides to tried-and-true agile and testing methods also ranked high. Check out the roundup. |
||
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. |
||
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. |
||
Does Your Boss Waste Your Time? It's good to eliminate any time-wasting practices, but that can be tricky when they come from your boss. Manager-imposed time wasters include micromanaging, holding unneeded meetings, requiring unnecessary status reports, and issuing ambiguous instructions. Here's how to broach the subject and get some time back. |
||
Make the Most of Your Downtime with the 3 P’s Downtime doesn’t need to mean unproductive time. It doesn’t have to be spent passively waiting for your next assignment. Instead, you can take advantage of your downtime and use it productively. If you want to maximize your downtime but don’t know where to start, focus on the three P’s: product, process, and people. |
||
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. |
||
6 Signs Your Agile Project Isn’t Really Agile There's a trend of organizations declaring they are agile without actually changing how they develop software. Declaring that an apple is an orange doesn’t make it so. These six key indicators can help you determine whether your agile project isn’t really agile after all—and give you some solutions to help. |