STARCANADA 2019 - Agile Testing

Automation is critical in today’s software delivery lifecycle, and yet many organizations struggle to keep their automation running. How can we mitigate difficulties and get consistent automation runs and results we can trust? The secret is implementing a solid automation framework, but that isn’t as easy as it seems. Chris Loder has built several automation frameworks over his career and has learned what works—and, more importantly, what doesn’t. This tutorial will cover what an automation framework is, the benefits of having one, and the keys to a successful framework, including...

Product owners and stakeholders love to ask about performance. “Is the app fast? How fast?” What do those questions even mean? Are they interested in the number of transactions per second? The time for the page to load? How many users it can support at once? Performance testing is a much broader topic than just being able to say an application is “fast” or “slow.” There is load testing, stress testing, and soak testing. You can measure transaction times, concurrency, and capacity. You can address some performance issues with more systems, others with more memory or faster processors or a...

Delivering hundreds of laser beams to brain tumors with sub-millimeter precision requires accurate, safe, and effective software that is developed and tested carefully and meticulously. But to be competitive in the market and responsive to customer needs you’ve got to be fast. How do you satisfy this contradiction? How do you know when the software is ready? When is good enough, truly good enough? Are you fast enough, and are you compliant? In two-week sprints, Zap Surgical develops software for planning brain cancer treatments, and then delivering those treatments on its new gyroscopic...

One of the lines in the Agile Manifesto is "Working software over comprehensive documentation." This doesn't mean that no documentation is produced, but instead that only documentation that brings value to the team and the customer should be created. So what do you do when you are working in a regulated industry and you need to produce extensive documentation to prove that the system works correctly? Jonathan Kauffman recently worked with a company that produces FDA Class II medical devices and wanted to reduce the overhead of creating the documentation required by regulatory...

How do you know your feature is working perfectly in production? If something breaks in production, how will you know? Will you wait for a user to report it to you? What do you do when your staging test results do not reflect current production behavior? In order to test proactively as opposed to reactively, why not test in production?! By testing in production, you will have an increased accuracy of test results, your tests will run faster in production due to elimination of mock/bad data, and you will have a higher confidence before releases. You can accomplish this through feature...

Everything starts with a requirement—a singular, documented need that a particular design, product, or process aims to satisfy. No other part of our work paralyzes the resulting system if it is done wrong, and no other part is more difficult to repair later. And yet we devote so little attention to requirements. By teaching people who create requirements, Arnika Hryszko learned a lot about their ways of working. She will share those lessons so that you will be able to improve your teams and projects by establishing detailed technical requirements. Discover practical ways to plan...