Related Content
 |
Testers Must Use Team Connections to Enable Quality The quality team has the greatest reach in its visibility and ability to connect with all other engineering and non-engineering teams. For a tester to realize their fullest potential, they need to acknowledge and leverage this reach by communicating and collaborating with all other teams to create the best product. |
|
 |
2 Ways to Standardize QA Practices Testing can get complicated when each project is using a completely different toolset, language, and reporting status, with different measurements and formats. Testing is a reaction to context and what we encounter, so how we test cannot be standardized. What we can standardize is the stuff that surrounds the testing. |
|
 |
Getting Support for the Tests You Need Done It’s often hard for teams to get sufficient time and resources for the amount and quality of tests they think are needed. It’s like management wants testing done but at the same time doesn’t want to commit what’s needed to do it. If that's your case, look at the business side, rank priorities, and negotiate resources. |
|
 |
7 Essential Quality Attributes for Your Test Automation Framework A common problem in software is that developers and designers tend to concentrate on pure functionality and neglect quality attributes. These are the famous “-abilities”: usability, reliability, portability, etc. If your testing framework is suffering, you might want to check if it has these seven quality attributes. |
|
 |
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. |
|
 |
The ‘Third Rail’ of Project Management: Cutting Quality Scope, schedule, and resources: Whether you’re using agile or more traditional project management approaches, this triple constraint is the law of the project universe. The unmentionable “third rail” of project management trade-offs is compromising quality to deal with the other two aspects. Don't make that an option. |
|
 |
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. |
