Related Content
A Lean, Flexible Measurement Dashboard for Agile and DevOps If you’re moving from a more traditional software development approach to agile and DevOps, or if you’re struggling with implementing metrics, consider reviewing, revising, and refining your measurements. Leave those that add no value behind and look at a monitoring system that has these five essential categories. |
||
What’s in the Fall 2017 Issue of Better Software Magazine Better Software magazine editor Ken Whitaker highlights content from the latest issue, including articles on bridging the divide between agile and waterfall, scaling agile through empowered teams, DevOps and IoT, and continuous development. |
||
Use Continuous Backlog Grooming to Refine Agile Requirements Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help. |
||
Becoming a Modern Software Tester Testers today need to look more like developers than users. Automation is becoming essential, so understanding at least basic programming is a must. As companies adopt agile and deliver more frequently, modern testers should learn to code, understand continuous integration, and use tools to eliminate constraints. |
||
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. |
||
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. |