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. |
|
 |
Why API Testing Is Mission-Critical With API testing, if you change how the API works—even if it now works better—it will break all of the code written by people using the API. Consequently, testers have a responsibility to make sure they are testing the same contract that was established when the API was first released. Here's how to test APIs right. |
|
 |
5 Steps to Stable Continuous Testing in DevOps Continuous testing minimizes risk and ensures DevOps has the tools to deliver quality, modern code that is ready for the future. To fulfill this, you have to first understand the three types of personas in testing. Then, you'll know how to work with them to progress along the path toward achieving continuous 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. |
|
 |
Are Your Retrospectives Adding Value to Your Scrum Team? Sprint retrospectives are often skipped, compressed, or organized in a way that doesn't provide good feedback. This is unfortunate, as a well-planned retrospective is a great way to improve how you work. Good retrospectives enable engagement and safety, distill and prioritize ideas, and create concrete action items. |
|
 |
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. |
|
 |
Testing Uncertainty: Strategies for Testing a Chatbot Testing chatbots differs a lot from “traditional” testing, like for an app or web portal, due to the apparent randomness of a conversation with a chatbot. For testers to have a better understanding of working with chatbots, they have to apply critical thinking to deal with the uncertainty in their test objects. |
|
 |
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. |
