Related Content
Picking the Right Test Automation Tool Take the time to evaluate your team and your goals before committing to automation, and be sure to try out different tools instead of following what might be popular at the time. Automation is critical, but bad automation will only slow down your processes and sink your projects. |
||
Getting Started with API Testing For testers interested in moving into test automation, Justin Rohrman usually suggests that they get started by learning to write a little code—more specifically, working with their software's API. You don't have to jump into tooling just yet. You can begin testing the data and workflow of the API first. Here's how. |
||
Agile Testing Shouldn’t Change Based on Team Size It’s important to note the more collaborative nature that agile encourages for every single member of the team—not just the testers. Sure, testers might have to adopt the most new skills if they hope to make things work at this new pace, but product owners and developers can’t just rest on their laurels. |
||
Craftsmanship: The Software Testers’ Goal Some people just don’t care about creating great products or services. They believe the marketplace will settle for lower quality. Lee Copeland argues that as software testers, we need to combat that way of thinking by embracing craftsmanship. Focus on quality with knowledge, skill, diligence, judgment, and passion. |
||
How to Make Agile Work for Your Specific Team Taking a step back, being honest about your strengths and weaknesses, and then using agile concepts to make yourself better is smarter than simply copying another team's structure. Agile can be your base, but don’t let trends that work for your competitor dictate the core of your software development. |
||
What Testers Need to Know about Security Every single tester should keep an eye on what security vulnerabilities might be plaguing their testing, but speaking in an interview at STARWEST 2016, Jeff Payne, the CEO and founder of Coveros, explained why you need to put a focus on security very early in the process. |
||
Avoiding Continuous Bugs: Speed and Quality in DevOps Lots of DevOps initiatives focus on speed and frequency of deployment without an emphasis on quality. Bad testing practices in DevOps only deploys buggy software faster. Here are some tips to move toward a more effective testing process that supports a continuous delivery approach—without sacrificing quality. |
||
Continuous Integration Makes Testers Look Like Developers There have always been distinct lines that separate developers and testers—and they didn’t often work all that close together. However, shifting everything to the left and being more concerned with testing at every single stage of development has blurred the line between their responsibilities. |