Related Content
Quality Engineering in Agile and DevOps Ensuring that quality is advocated for at every step along the lifecycle can be tough. One easy response is, “Quality is everyone’s job”—after all, whole-team accountability is a key tenet of agile. But what does this really mean in practice? What approaches and roles help us embrace a culture of quality engineering? |
||
Making (and Keeping) Project Risk Visible Project managers recommend how much should be invested to address various risks based on their understanding of project context, but the final decision about what to do and when those efforts are sufficient belongs to the sponsor. Risk management requires executive input, so sponsors need to see all risk data you have. |
||
Good Process, Bad Process “Process” is a word that seems to have a lot of baggage. Depending on whom you ask, process is either essential to delivering value, or something that gets in the way. But this is the wrong way to frame the issue. A process is not inherently good or bad; it's how you use it, and whether it's right for your situation. |
||
Stop Releasing Untested Defect Fixes into Production Releasing untested defect fixes into production is a real possibility. Being aware of how this can occur may help reduce the possibility of it happening. Let’s explore the common reasons defect fixes go untested—insufficient testing or resources, and undocumented fixes—as well as the steps we can take to prevent them. |
||
Testing in a Modern World: A Slack Takeover with Janna Loeffler Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Janna Loeffler, QE manager for Ultimate Software, hosted this Slack takeover and discussed all things testing, how the role of a tester is shifting, and navigating a career as a woman in tech. |
||
To Be a Better Tester, Ask the Right Questions Critical thinking is a core trait a software tester needs to succeed, and asking questions is a great skill to help. Questioning brings out the required information, breaks assumptions, and enables everyone on the team to give their perspectives. But there's an art to asking the right question at the right time. |
||
Pros and Cons of Codeless Test Automation To create automated tests for software applications, testers have historically needed to be able to code in programming languages. Codeless testing eliminates the need for scripting from scratch every time, but in addition to its advantages, there are also some drawbacks. Is codeless automation right for your team? |
||
2 Ways to Get Better at Test Automation Many people in testing roles want to grow their skills and learn to build some tests with code. But no matter how well you test, automation is programming work. If you want to get better at automation, your best bet is to get into a role where you are dealing with code. Here are two ways you can break in and learn. |