Related Content
 |
A Simple Rule of Thumb for Unit Testing There's a simple rule for the minimum values testers should explore: “none, one, some”—or, how the software behaves if you send it nothing, one thing, or some set greater than one. It's not comprehensive, but it gives a good feel for how the feature works at the moment. Developers can also use this in unit testing. |
|
 |
Providing Value as a Leader: More Than Just Being the Boss As a leader, your job is not to be the boss and check on every task, but to provide value to your team, helping them grow, learn to fix things, and make decisions without you. One of the best ways to provide value is by asking questions. Questions clarify expectations, confirm understanding, and build relationships. |
|
 |
Using Agile to Navigate through Medical Device Regulations When you test medical device software, you must be very careful. But when development wants to push a cadence of two weeks per sprint, every sprint, you’ve just got to keep up! Interpret the regulatory requirements not as a set of disabling constraints, but as a challenge to find the optimal route to navigate through. |
|
 |
Testing, Today and Tomorrow: Slack Takeovers with Arthur Hicken and Aprajita Mathur Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Arthur Hicken and Aprajita Mathur each recently hosted Slack takeovers, and they talked about keeping IoT devices secure, onboarding new test team members, and what skills we should be learning. |
|
 |
Lower Risk of Downtime by Testing with Production Traffic Teams need a means of identifying potential bugs and security concerns prior to release—with speed and precision, and without the need to roll back or stage. By simultaneously running live user traffic against the current software version and the proposed upgrade, you can detect bugs while reducing risk and downtime. |
|
 |
How Embracing Differences Makes More Robust Agile Teams On any team, there are bound to be some differences. But even though work styles may differ from what you expect, they may not be problematic simply because they are different. Before making assumptions about what a teammate is doing or why, just ask to find out. Their differences may bring a helpful new perspective. |
|
 |
Creating a Community of Testers Many teams are divided by product or feature, with only one dedicated tester per team. How do you learn and grow in your career when you’re disconnected from your peers? One solution is to create your own community of testers that spans the organization. Here are some ideas to start and facilitate a Quality Guild. |
|
 |
Stop Email Overload and Communicate Better Many of us fire off correspondence to groups and distribution lists that include more recipients than necessary, and we overcommunicate without stopping to think about exactly what needs to be conveyed. Here are some ways organizations and teams can cope with the influx of information and communicate intentionally. |
