Related Content
 |
Making Testing Work within Your Sprints A common problem for Scrum teams is having a good understanding of what work is complete by the end of the sprint. Teams often end with a few items coded but not fully tested, but since the goal of a sprint is to have a deliverable increment of work, skipping tests isn’t a good idea. Here's how you can fit them in. |
|
 |
Choosing a Font for Software with a Global Audience As more businesses are establishing a worldwide presence, our approach to software must consider globalization and localization. So when it comes to designing the user interface for our apps and websites, we must consider good typography. Here's what to take into account when choosing fonts for international products. |
|
 |
5 Ways to Shift Performance Testing Left Performance testing is often a barrier to accelerating software delivery. Because you need a production-like environment, performance testing often waits until the entire application is complete. But you shouldn't wait until then to get started. You can begin testing earlier to reduce rework and address issues sooner. |
|
 |
Scrum Can Help You See the Forest and the Trees In project management, it's easy to focus on details to the extent that you lose track of the larger goal. Scrum can help you identify flaws and gaps, and skipping or trivializing Scrum events will just hide the fact that there are things you need to improve. Finding problems is something to be celebrated, not hidden. |
|
 |
How DevOps Has Changed the Landscape of Testing The focus on automation and “continuous everything,” from integration, deployment, and now all the buzz about continuous testing, makes the daily activities of a tester in DevOps challenging. Testers may be used to controlling quality—or thinking they do—but they need to pivot to assuring their teams focus on quality. |
|
 |
Testing When There Are No Testers More and more companies are shifting toward having their developers responsible for product quality. But how do you conduct good testing when there are no testers? The key is to optimize efforts. Here are some of the fundamentals of testing that your developers should understand, as well as some skills they'll need. |
|
 |
Testers as Disciplinarians As testers, are we disciplinarians? We shouldn't fall into the trap of controlling quality or becoming quality police. Instead, we should be true facilitators of quality, enabling the product team to own it in their own right at every stage. Isn’t this what teachers do, too, in the learning process? What is our role? |
|
 |
Overcoming Test-Driven Damage Some say test-driven development may work well initially, but as soon as we start to refactor our code, it breaks old tests and requires us to write new ones. This is not the fault of TDD; it’s the way we’re using it. TDD remains a valuable way to verify code as we write it, so we need to repair our test-driven damage. |
