Testing and Quality Assurance
 |
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. |
|
 |
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. |
|
 |
Get Your Defect-Tracking Database Back on Track When defects are ignored or mismanaged, it can compromise the integrity of the defect-tracking database. When this happens, defects could go unfixed, or code fixes may not be verified by the production release. Before you can resolve a compromised defect-tracking database, you need to know how to recognize one. |
|
 |
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. |
|
 |
The Present and Future of AI: A Slack Takeover with Raj Subramanian Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Raj Subramanian, who works with self-healing, AI-based test automation, hosted this Slack takeover to discuss all aspects of AI: testing it, its biases, where it is now, and where it's going. |
