Agile2017 has ended

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Testing & Quality [clear filter]
Tuesday, August 8

3:45pm EDT

Writing better BDD scenarios (Seb Rose, Gaspar Nagy)
Limited Capacity seats available

Behaviour Driven Development is an agile development technique that improves collaboration between technical and non-­technical members of the team, by exploring the problem using examples. These examples then get turned into executable specifications, often called ‘scenarios’. The scenarios should be easy to read by all team members, but writing them expressively is harder than it looks!
In this 75 minute workshop you will learn how to write expressive BDD scenarios. We’ll start by giving you a very brief introduction to BDD/ATDD. You’ll then be introduced to different writing styles by reviewing pre­prepared scenarios. Finally, you’ll get a chance to write your own scenarios based on examples that we’ll bring along.
We’ll be using Gherkin, the syntax used by Cucumber and SpecFlow ­ but you won’t need a computer. And, you'll leave with a checklist of tips that you can use the next time you sit down to write a scenario.

Learning Outcomes:
  • - Identify common Gherkin pitfalls
  • - Write compact, readable living documentation
  • - Enumerate 5 tips/hints for writing good scenarios
  • - Explain the difference between essential and incidental details
  • - Describe how precise, concrete examples illustrate concise, abstract rules/requirements/acceptance criteria
  • - Use the Test Automation Pyramid and Iceberg to convince colleagues to mention the UI less in scenarios


avatar for Gaspar Nagy

Gaspar Nagy

coach, trainer and BDD addict, Spec Solutions
I am the creator and main contributor of SpecFlow, regular conference speaker, blogger (http://gasparnagy.com), editor of the BDD Addict monthly newsletter (http://bddaddict.com), and co-author of the book "BDD Books: Discovery - Explore behaviour using Examples" (http://bddbooks.com... Read More →
avatar for Seb Rose

Seb Rose

Director, Cucumber Limited
I have been involved in the full development lifecycle with experience that ranges from Architecture to Support, from BASIC to Ruby. I'm a partner in Cucumber Limited, who help teams adopt and refine their agile practices, with a particular focus on collaboration, BDD and automated... Read More →

Tuesday August 8, 2017 3:45pm - 5:00pm EDT
Wednesday, August 9

10:45am EDT

Building Agility into regulated mobile software testing projects (JeanAnn Harrison)
Limited Capacity seats available

Working on a regulated product requires certain goals to be met to satisfy regulated auditors along with balancing out achieving test coverage to release a high quality mobile software product. Testing mobile apps can be complex task but adding the goal of meeting regulations can be overwhelming.
Team members must work together to blend meeting regulations, understand user experience tests based on priorities and severity levels to allow for iterative sprints. Testers and Developers need to communicate the inter-dependencies and include prioritized user stories based on severity levels which will help to achieve that high level of test coverage and avoid high risks.
How a tester works with their project team will be key achieving agility in these software projects. Jean Ann will present techniques to inspire project teams to develop what will work best for their company culture.
This session will cover:
1. Mobile App project teams must establish risk management and actionable mitigation tasks prior to each project release. Teams work to establish priorities and severities based on User stories. 5 min
2. Testers work with project team members to help develop test ideas based on the user stories and assigning those stories considering severity and priority. 5 min
3. Group exercise: Create test ideas of a mobile app based on a provided user story for a medical device. Think about severity and priority for users, for project team, for regulated auditors. 15 min
4. Testers & developers are tasked to build quality not only in the mobile app itself but also the inter-dependencies of a full system approach. 15 min
5. Group Exercise: Create a test where an inter-dependent condition could affect software behavior. 15 min
6. Testers provide responsive feedback on the user stories, the testing conducted while the mobile app is being developed through iterations and meeting regulations. 10 min
7. Questions 10 min

Learning Outcomes:
  • 1. Testers will work with project team to incorporate quality and meeting regulations early in planning tests for mobile projects in a regulated environment.
  • 2. Testers will help project team members to create user stories with priorities and severities assigned giving testers specific goals to focus with each sprint.
  • 3. Testers will understand to work closely with development which inter-dependencies can affect how users will be affected by the mobile app.



Wednesday August 9, 2017 10:45am - 12:00pm EDT

2:00pm EDT

Three Practices for Paying Ongoing Attention to System Qualities (Rebecca Wirfs-Brock)
Limited Capacity seats available

Does your team have trouble focusing on anything other than implementing features? System qualities such as performance, maintainability or reliability don’t happen by magic. They need explicit attention and focus. What can we as system quality advocates—whether testers, developers, product owners, architects or project managers—do to raise awareness of the qualities of our systems? You’ve probably heard the mantra: make it work, make it right, make it fast. But it can be difficult to retrofit certain qualities into an existing implementation. Making it right means more than verifying the functionality meets stakeholder needs; it also means delivering on the qualities we want in our system. In this session you will be introduced to three simple techniques for specifying system qualities and paying attention to them: landing zones, quality scenarios, and quality checklists. You will also have an opportunity to briefly practice each technique. Yes, you can introduce simple practices that allow you and your team to pay ongoing attention to system quality.

Learning Outcomes:
  • Learn how to use and define a landing zone for key quality attributes
  • Understand the mechanics of writing a quality scenario for "normal" and failure/recovery actions
  • Understand how to co-create two kinds of quality-related checklists: do-confirm, and read-review
  • Learn how to identify natural pause points in your work where checklists can be useful


avatar for Rebecca Wirfs-Brock

Rebecca Wirfs-Brock

Wirfs-Brock Associates
I'm best known as the "design geek" who invented Responsibility-Driven Design and the xDriven meme (think TDD, BDD, DDD..). I'm keen about team effectiveness, communicating complex requirements, software quality, agile QA, pragmatic TDD, and patterns and practices for architecting... Read More →

Wednesday August 9, 2017 2:00pm - 3:15pm EDT
Wekiwa 6
Thursday, August 10

10:45am EDT

API Testing FUNdamentals (JoEllen Carter, Dan Gilkerson)
Limited Capacity filling up

Applications increasingly talk to each other behind the scenes via APIs. Google’s recent acquisition of Apigee, an API management company, is a strong indicator of the continued importance of APIs in software development. APIs are like building blocks, providing services and data that can be connected with other APIs to build powerful customized apps. However, testing an API can be challenging for these reasons:
  • There is no built-in interface
  • Breaking changes can cause widespread outages
  • Sensitive data may be exposed or accessed
  • Accepted testing paradigms can be difficult to adapt to APIs
In this workshop, you will learn how to fearlessly approach testing an API even if you've never heard of HTTP or cURL. In particular, you will learn:
  • Current business trends that are driving API development
  • Components of HTTP requests and responses, including authentication models, and how to inspect HTTP traffic
  • How to ‘explore’ an API and get some hands-on practice using popular tools
  • Tips on how to design tests for security, performance and backwards-compatibility risks
  • How to incorporate juggling, magic, and standup comedy into your tests (courtesy of Dan)

Learning Outcomes:
  • APIs and application architecture - Why APIs are important
  • HTTP basic info
  • How to turn an HTTP request and response into a 'test'
  • Exploratory testing heuristics particularly valuable when testing an API
  • Recommended tests for any API


avatar for JoEllen Carter

JoEllen Carter

QA Manager, Olo, Inc.
I work at Olo! At Olo, we develop an online food ordering platform used by many of the country’s largest restaurant chains, reaching millions of consumers. Our highly skilled team of testers supports weekly releases and a constantly changing architecture as we transition to a... Read More →

Thursday August 10, 2017 10:45am - 12:00pm EDT
Wekiwa 5
  Testing & Quality, Workshop