Related Content
 |
Web Services Need Some Testing Love, Too Web services—the applications that talk to other applications—are generally finished before the GUI, so you can test the business logic before you think about the actual interface. You can improve the quality of your application, find interesting bugs that don’t exist in the GUI, and give web services some love. |
|
 |
The Real Value of Shifting Your Testing Left When you take a quick, general look at what shifting left means, you might wonder how it makes things faster. Testers are testing earlier and more often, so that means more work throughout the entire project lifecycle. Shouldn’t that slow things down? |
|
 |
Assemble an Efficient Mobile Device Farm to Maximize Your Testing Mobile testers need to know which devices and operating systems are in demand, but you don’t want to have to maintain (and test) every device on the market. Here’s how you can set up the most relevant farm of mobile devices so that you can feel secure that your application will work correctly for most of your users. |
|
 |
Using Systems Thinking to Extend Your Test Automation Power When automated tests work perfectly one day but fail for no discernible reason the next, it's easy to get frustrated with automation. But you don't have to stay in the dark. Many of the tools we use today allow us to extend their reach with some custom code. Just use some systems thinking and a little imagination. |
|
 |
Automation Needs Strategy, Leadership, and Real Testing Skills The people behind your automation tools need to understand how the testing is done. You want your automation people to be able to write their own test cases, understand the domain so that they know what they’re automating should be automated, and have an overall solid testing foundation. |
|
 |
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. |
