Related Content
 |
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. |
|
 |
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. |
|
 |
Key Enablers for Continuous Testing Continuous testing means testing before, during, and after each software change is made. Testers have long advocated for this, but DevOps has made it more popular by pushing for rapid feedback and shifting testing left in the lifecycle. Here are three practices your company should embrace to enable continuous testing. |
|
 |
Designing Data Models for Self-Documented Tests When testing applications, documenting and interpreting test results can be a challenge. Data models enable us to collect and process test data more dynamically and uniformly. To design effective data models for self-documented tests, there are three important things to consider: what to document, collect, and report. |
|
 |
Change Is Hard, but BDD Is Worth It Behavior-driven development is a methodology change that impacts the whole team, and unfortunately, it’s not as easy as writing scenarios in a specific format. What is the added value of BDD? Why should the team throw their current process out the window and try to incorporate a new methodology? Here are some reasons. |
|
 |
When Field Testing Isn’t Possible, Use Simulation Field testing is great for discovering different situations, but due to a variety of constraints, it may not always be possible. In such cases, simulation is useful to create a picture that mimics the real scenario. You can replicate hardware, operating systems, network ranges, and more, as well as nonfunctional areas. |
