Related Content
 |
Why Do We Test Software? "Why do we test software?" seems like a silly question—most people would say, “So we know it works, duh." But there are many other reasons we test our products, as well as many possible benefits besides confirming that a system does what we intended it to do. Figuring out the purpose behind your tests is illuminating. |
|
 |
Simplify Your Record and Playback UI Automation Record and playback shouldn’t be a nightmare to deal with. One key for useful UI automation in any tool is abstracting at the right level. Take a cue from coded solutions like WebDriver and its Page Object pattern, and do something similar with record and playback tools to abstract away all the scary bits. |
|
 |
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. |
|
 |
How to Stay Happy in Your Testing Career Jon Hagar believes a tester should have fun, find their work challenging, and look forward to an interesting career. Some great ways to achieve this job satisfaction are to keep learning and updating your skills, develop a career plan for the future, and seek out the fun challenges in software testing. |
|
 |
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. |
