The concept of accessibility has been around for more than twenty years, yet it’s only recently that more companies have started including it in their development efforts. Developers and testers are recognizing the advantages of incorporating accessibility techniques into their processes. Here are some of these methods specific to agile software development, including a handy checklist.
Uncertainty has always been a key challenge for testers. But testing a chatbot adds a completely new level of uncertainty. There are a lot of platforms and tools available for chatbot development, but what we lack is a standardized chatbot testing strategy.
Globally distributed software teams are no longer just a trend—they are industry commonplace. Creating these teams allows companies to lower their costs by tapping into developing markets and to provide support around the clock.
Having regular one-on-ones is the key to supporting employee performance. As a leader, you know regular conversations are important. When can you find time? How can you make them more productive? What can you do to make them valuable to both you and your team member? What is the benefit to the organization? As a manager of a 50+ testing team, Dawn has successfully rolled out a one-on-one format that produced an increase in team performance across the organization. She will share her experiences and lessons learned from NOT having one-on-ones, and show you how you can use your one-on-ones to establish trust.
The market demands that high-quality software is released at an increasing pace, yet resources remain fixed. How can organizations expand and improve testing under these conditions and help prevent costly and embarrassing bugs in production software?
Many agile teams rework previously deployed stories, even after plenty of in-sprint testing. Well groomed, refined, stories framed with typical, alternate and error scenarios, gracefully described in well formed gherkin, continue to encounter all sorts of bugs.
If something breaks in production, how will you know? Will you wait for a user to report it to you? What do you do when your staging test results do not reflect current production behavior? In order to test proactively as opposed to reactively, why not test in production?