Software Testing

Tutorials

MB Software Requirements Fundamentals for BAs, Testers, and Developers NEW

Lee Copeland, Software Quality Engineering

Mon, 11/10/2014 - 8:30am

You deal with software requirements all the time. Whether you are a developer in an agile environment, an analyst who identifies and documents requirements for plan-driven development, a software designer who studies requirements as the basis for agile development, a tester who employs or often must discover requirements as the foundation of test cases, or a technical user who describes your needs to development, you need the right approaches and skills to develop and interpret software requirements.

MK Continuous Integration and Deployment through Continuous Testing NEW

Jared Richardson, Agile Artisans

Mon, 11/10/2014 - 1:00pm

Continuous integration and continuous testing are two vital agile feedback loops that lead to a continuous deployment environment. Continuous integration monitors your source code―recompiling after every change, running smaller tests, and notifying the developer if anything goes wrong. Continuous testing (and potentially continuous deployment) monitors integration builds, installs the product in a staging environment, and runs integration tests, again looking for problems.

TH Agile Project Failures: Root Causes and Corrective Actions

Jeff Payne, Coveros, Inc.

Tue, 11/11/2014 - 8:30am

Agile initiatives always begin with the best of intentions—accelerate delivery, better meet customer needs, or improve software quality. Unfortunately, some agile projects do not deliver on these expectations. If you want help to ensure the success of your agile project or get an agile project back on track, this session is for you. Jeff Payne discusses the most common causes of agile project failure and how you can avoid these issues—or mitigate their damaging effects.

TS Specifying Non-Functional Requirements NEW

John Terzakis, Intel

Tue, 11/11/2014 - 1:00pm

Non-functional requirements present unique challenges for authors, reviewers, and testers. Non-functional requirements often begin as vague concepts such as “the software must be easy to install” or “the software must be intuitive and respond quickly.” As written, these requirements are not testable. Definitions of easy, intuitive, and quickly are open to interpretation and dependent on the reader’s experiences. In order to be testable, non-functional requirements must be quantifiable and measurable.

Keynotes

K1 From Chaos to Order—Leading Software Teams Today

Ken Whitaker, Leading Software Maniacs

Wed, 11/12/2014 - 8:30am

To successfully lead “the nerd herd,” you’re expected to motivate your team to perform, encourage innovation, and produce software solutions that delight the customer. Prioritizing your time for what’s most important can be quite challenging—especially when you’re swamped with a steady stream of incoming requests, meeting overload, and the ever-present personnel issues. The expectation of even faster product deployment, the evolution of software development to agility, and the establishment of self-directed teams often require even more time devoted to planning.

Concurrent Sessions

AT4 Establishing an Agile Testing Culture

Leigh Ishikawa, TripAdvisor

Thu, 11/13/2014 - 10:00am

Many resources describe how to accelerate performance of your development organization through adoption of agile methodologies, but very few cover testing in a practical manner. And those that do generally focus on technical details, leaving out how to build an agile testing culture while facing numerous adoption challenges. Leigh Ishikawa describes how an organization needs to rethink testing in the agile world. He begins by taking a holistic look at how different groups combine in an agile testing culture.