Related Content
 |
Preventing Boring Test Syndrome in Your Automation Boring tests are easy to spot: A good rule is if you start feeling sleepy after a few minutes of looking at them. Although routine tests may still find quality issues, having to write them will not encourage a tester to be creative in challenging the application. Here are some ways to make tests more interesting. |
|
 |
Career Options for Testers in the Age of Agile and DevOps Software testing expertise is still a critical need. But as we enter the age of agile and DevOps, the industry is changing. If you’re in a software quality or testing role now as a direct contributor or leader, how should you prepare? What’s your next career step? Here's how you should equip yourself for the future. |
|
 |
Succeeding in the World of Test Automation: A Slack Takeover with Paul Grizzaffi Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Paul Grizzaffi, principal automation architect for Magenic, hosted this Slack takeover and discussed how to choose a tool, getting automation projects going, and future-proofing testing careers. |
|
 |
Don’t Let “Try It Now” Impede Your Test Initiative Sometimes environmentally based issues arise that impede your ability to access or test the software. Rather than addressing the problem methodically, as with defects, testers often attempt to solve it on their own. Here's why entering the problem into the defect-tracking database is a more efficient way to solve it. |
|
 |
2 Ways Developers Can Contribute to Better Testing Testers need to find important information about product quality and present it in a way that can be acted upon. As the people building the software, developers are in a great position to observe the product. By monitoring the test environment and conducting unit testing, they can help inform about product quality. |
|
 |
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. |
|
 |
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. |
