Related Content
 |
The Testing Practices and Metrics That Really Matter in Agile and DevOps Scaled agile and DevOps change the game for software testing. It’s not just a matter of accelerating testing; it’s also about fundamentally altering the way we measure quality. The test outcomes required to drive a fully automated release pipeline are dramatically different from the ones most teams measure today. |
|
 |
Lessons Learned in Testing a UI Test Automation Tool How do you test a tool to be used for automated testing? If a tool executes an automated test that generates keyboard and mouse events to replay user actions, can the test emulate user input and control another instance of the tool to automatically record and play another test? Here's how you test the test tool. |
|
 |
Yes, She Can STEM—and More Many girls begin losing interest in STEM subjects as early as middle school, and this path continues. #SheCanSTEM is a new public service media campaign that hopes to encourage middle school girls to ultimately pursue STEM careers by challenging stereotypes and showcasing female STEM role models. |
|
 |
How to Prioritize Tasks and Do Only the Work That Matters When you’re working on multiple projects at a time and everyone is breathing down your neck for results, it’s difficult to separate wants from needs. You have to be smart about task prioritization. Here are four ways to break through the noise and make sure you’re focusing on the work that really matters. |
|
 |
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. |
|
 |
Looking beyond the Tester-to-Developer Ratio Many companies have some notion of an ideal tester-to-developer ratio, or the number of testers they need for every certain number of developers. It may seem like a superficial standard, but it's rooted in a very real need to understand staffing requirements and budgets. Let's dig deeper into the team balance. |
|
 |
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. |
|
 |
Testing at 43,000 Feet: Reporting Risk That Matters Many teams' daily testing gets broken down into numbers. If you're used to dashboards, it can be easy to forget the prime objective: to raise up quality issues—or, in the case of safety-critical devices, potential hazards. Graphs are comfortable, but do they really provide the information we should be looking for? |
