2015 Conference Presentations


All available talks are embedded below and stored on SlideShare here

Anna Royzmananna royzman Ready, SET, Go!In this dynamic presentation, Anna will reveal the mindSET and skillSET of the champion tester. She will be explaining the concepts of context-driven testing to a wider QA community, and focusing on testing skills and practices that complement and enable the high-performing agile delivery team.

Benjamin Winklerbenjamin winklerKelli Searfoskelli searfos Eight Bad Testing IdeasGetting your scenarios from the developer.  Using random data.  Changing the test to fit the code.  This session explores what NOT to do in testing — tried and true recipes for brittleness, unmaintainability, or tests that are secretly useless.  In this session, we look at QA antipatterns to identify certain “worst practices” in automated software testing, and how to avoid stumbling into them.
Damian Synadinosdamian synadinos Improv(e) Your Testing! Tips and Tricks from Jester to Tester Improvisational Comedy (also called Improv) is a form of theater where the performance itself is created in the moment. Successful improv involves using a variety of skills and techniques, which allow performers to quickly adapt to a constantly changing environment and new information. Now, reread the last sentence, but replace “improv” with “testing”. This mildly interactive presentation will highlight a few of the many similarities between improv and testing. Creative metaphors and critical analysis will provide novel and notable ways to think about testing. From stage fright to test summary report, and everything in between…attendees will laugh, learn, and leave with knowledge to help Improv(e) Your Testing!

Jess Lancasterjess lancaster Show It!: Better Testing through Visual CommunicationTesters can spend a lot of time managing test documentation through the test execution process. They need efficient and effective methods for sharing test information, such as test results, bugs, and status. Applying visual communication techniques can help! In this session we’ll focus on visual communication concepts, and why you as a tester should be communicating visually. Then we’ll look at some real-world visual communication tips and techniques you can use to improve.
Jim Holmesjim holmes Developer/Tester Collaboration: The Practical SideThis talk shows attendees practical places where testers and developers can (and should be!) collaborating more frequently: creating better test cases, bringing software engineering fundamentals to automated tests, creating testable systems, and more.Developers will learn how working more closely with a tester can help them get better coverage in unit and integration testing. They’ll also see how they can help testers write much better functional tests via slight modifications to their applications’ user interfaces.

Testers will see how developers can help them create simpler functional test suites by learning software design concepts like Don’t Repeat Yourself (DRY) and Single Responsibility Principle (SRP).

All attendees will leave this session with a better understanding of how effective collaboration between testers and developers can dramatically boost the final quality and suitability of your delivered systems.

His talks can be found here https://speakerdeck.com/jimholmes/developer-tester-collaboration-the-practical-side

Joe DeMeyerjoe demeyer Challenging Your Project’s Testing MindsetsParticipating on a project as a Tester has some interesting contrasts and some unexpected experiences when compared to participating as a Developer. Having experienced both, I was most surprised with skepticism, concern, general invisibility, and subtle questions about my qualifications as a Tester. It seemed because I was a Tester, I had no credibility.The start of the project is the best time to make an impression, establish your identity, and build credibility.   Every Tester knows this but many times other priorities interfere with establishing a foundation for working with other team members and providing value to the project as a Tester.

In this session, I present an approach to challenging mindsets and establishing credibility: be available, visible, and vocal. Be available to meet team members, be visible at introductory meetings, be vocal about the role of testing in your project. Building upon these lays the foundation for participation in key meetings, improving testability, getting bugs fixed, and engaging team members in testing.

The session includes tips for participating in requirements, design, and code reviews. It concludes with methods of building credibility with your testing team, using delegation to build new test leaders, and advocating for testability in project products.

Jon Krugerjon kruger Iteration Management – Your Key to Predictable DeliveryProject managers might manage multiple teams across multiple iterations, but an iteration manager is responsible for making sure that one team can deliver within a single iteration.  Whether you’re looking for a new career path or trying to find a grassroots way that you can improve the software development process on your team, understanding iteration management will help you plan and estimate better, meet your commitments, communicate effectively with management, and not spend your weekends working to keep up.

Joseph Bealejoe beale Cucumber From the Ground UpAutomation is becoming more and more important in the world of software testing, especially as more development shops move into agile or agile-like methodologies. However, for testers with no development background the idea of learning how to automate can be intimidating.My goal is simple: to demystify the subject by taking a novice tester with no coding experience through the process of writing a simple automated test using using the Cucumber framework. I will take a volunteer from the audience and transform that person from an ordinary QA professional (or whatever their occupation) into an automation engineer in one short hour.

This will be a live demonstration and we will be working without a net. No animals will be harmed during the show, but be prepared to slay your fear of coding once and for all.

Joseph Oursjoseph ours Bad Metric, BadMetrics have always been used in corporate sectors, primarily as a way to gain insight into what is an otherwise invisible world. Not only that, “standards bodies”, such as CMMi, require metrics to achieve a certain maturity level. These two factors tend to drive organizations to blindly adopt a set of metrics as a way of satisfying some process transparency requirement.   Rarely do any organizations apply any statistical or scientific thought behind the measures and metrics they establish and interpret.   In this talk, we’ll look at some common metrics and why they fail to represent what most believe they do. We’ll discuss the real purpose of metrics, issues with metric programs, how to leverage metrics effectively, and finally specific measure and metric pitfalls organizations encounter.

Justin Rohrmanjustin-rohrman API checks for fun and profitIn this session Justin will discuss using your brain and other tools to test web and URL based APIs, including REST, in a practical way. Justin has spent much of the past year testing APIs at his day job and has learned a few lessons along the way. This is going to be part experience report of how Justin has been using API tools for the past year, and part demo of a few different tools he has come to enjoy working with. This session offers practical testing advice and experience that can be used daily.In this talk I plan to cover:

  • Introduction to APIs
  • Checking VS Testing
  • Tools
  • How this fits into your life

Attendees will take away:

  • Practical knowledge about API testing and checking
  • Free tools you can use tomorrow
  • Why you might want to start here rather than the UI
Kelsey Shannahankelsey shannahan Training for Automated Testing There is an immense interest in automated testing, especially in ATDD environments, but many testers lack the experience and knowledge to engage in it. While there are educational resources available, they are not necessarily targeted at people with no development background whatsoever. At Grange Insurance, we developed training for interested testers in order to elevate their skill set and provide them a foundation for participating in ATDD. This presentation will cover how that training was created and conducted, lessons learned, and steps for moving forwards after training is completed.

Ken De Souzaken desouza Feedback and its importance in delivering high quality software Broadly, feedback comes in three forms: appreciation, coaching and evaluation. Often the receiver wants to hear one type of feedback, while the giver actually means something else. In your testing career, you will need to understand how to give and receive feedback; from bug reports to discussion quality with executives. Ken will share his experiences of the feedback process during various points in his software development career.Areas where this type of information will help you:

  • Coaching: giving and receiving comments during test case and session-based reviews.
  • Evaluation: developing relationships with various levels of management where criticism is encouraged and used to move the organization forward.
  • Appreciation: helping to preserve the value of the software you are testing. Think bug reports.

Attendees will take away:

  • How to give and receive feedback, by identifying the various triggers
  • Ways of practicing it in a safe environment

Larry Albrightlarry albright Building and Sustaining a Software Development Organization’s Grass Roots Continuous Improvement Framework Have you been tasked with creating a Continuous Improvement framework for your software development organization but don’t know where to start? Would you like to set up an effective visual management board to collect, prioritize and track the completion of Continuous Improvement initiatives? Are you interested in changing your organization’s culture of operational excellence to generate new ideas from a grass roots level and manage improvement efforts more effectively?

Quality Assurance Analysts at Nationwide Insurance drive process quality improvements, as well as measure and analyze production process quality. As the Quality Assurance Lead for the Finance IT department, Larry Albright will share his organization’s journey toward empowering associates to drive Continuous Improvement with support from all levels within the department. The Finance IT Continuous Improvement framework encourages the collection, management and implementation of ideas at a local level by providing a consistent process and coaching. It also promotes communication and collaboration to keep Continuous Improvement initiatives moving forward, resulting in a positive cultural change for the organization.

Larry will present specific details of how the Finance IT Continuous Improvement process works and will show how the visual management board clearly communicates progress on improvement initiatives throughout the organization.

Matthew Eakinmatt eakin The Art of Gherkin Scripting With the creation of the cucumber framework came the creation of the Gherkin Scripting format (also known as the Given-When-Then format). The structure of a Gherkin script is very straight-forward: Given provides you with the background When tells you what is being created Then tells you the expected results. Writing a script in a Given-When-Then format may be fairly simple. Writing a good Gherkin Script is an Art. Some are Picassos, some are Monets, some look like they were created by a toddler with a crayon. In this presentation Mr. Eakin will offer some tips on writing good Gherkin Scripts and show you how a well crafted Gherkin Script can be a beautiful work of Art.

Matthew Heussermatt heusser Save Our Scrum Too many ‘Scrum’ teams are in trouble. Asked if they are “doing scrum”, the answer is more likely to be “ScrumBut”, “ScrumIsh”, “ScrummerFall”, “ScrumBan”, and so on.In this presentation Matt Heusser begins at the beginning – talking about what Scrum is – then moves very quickly to discuss the problems he has encountered, common solutions, and the consequences of those approaches. Come share your experiences in a talk designed to include conversation, sharing, venting, and, perhaps, a few ideas to implement back at the office to save the scrum.Scrum can help teams … and it can be misused. Come to this talk to find out what can be – and how to get there
Raj Subramanianraj-subramanian When Cultures Collide – A tester’s story What do these books have in common – “When Cultures Collide”, “Understanding Cultural Differences”, “Beyond Culture”? Yes, it involves people from different cultures trying to interact with each other and sustain in this diverse corporate environment which we now call – Our Workplace. This session is based on my real life experiences interacting, observing and working with people from different cultures, backgrounds, race, religion in a corporate environment.

As a tester, I had to understand and study how different verbal, oral and behavioral patterns are interpreted in different ways by different people. In this session, I try to highlight different communication patterns with examples. I will show how understanding and recognizing these patterns can help testers to sustain and collaborate with others. As the saying goes, “Solutions are often simple but getting to it is complicated”. Come join me as I share my research and experiences, and discuss how software testers can become more effective communicators.

Session Takeaways:

  • Understanding cultural differences in communication – verbal, oral and body language
  • Understanding different behavioral patterns and align our working style accordingly
  • Different ways to improve, to sustain in a diverse work environment

Shaminder Raishaminder raiDave Patelmissing-profilepic The Risky Business of Testing The assessment of quality requires an objective review of the solution against the requirements. The quality of the solution is typically measured by testing teams through well-defined tests that are written from requirements.   No amount of testing will prevent all defects, detect all defects, or prove a product is defect-free. There are too many permutations possible to completely test a system. Therefore, Risk Based Testing and its underlying principles: requirements validation, static testing, risk assessment, risk scoring, and risk driven testing are a necessity in defining and reaching quality expectations at the end of each testing phase. Furthermore, risk based testing provides both the IT Team and business stakeholders confidence in the quality ensured through the testing strategy. In this presentation, you will learn about how to implement a risk driven testing cycle and then measure your results. Was it worth it? Come find out!

Shawn Wallaceshawn wallace STOP! You’re automating too much! (and other tales from the field) Test automation has many advantages.   It is a useful but imperfect practice with limitations that are hard to anticipate in a new project. There are many questions that teams find themselves asking throughout a project’s lifecycle:

  • How do I get started?
  • What should I automate?
  • How do I collect the data?
  • How do I run my tests when no one is around?
  • Do I always need to run all of my tests?
  • Do I need to keep my tests forever?
  • Where does automation fit in the cadence of the team?

In this session we’ll discuss these question and some additional practical lessons learned from several years of building solutions that leverage test automation in both large and small environments.

Todd Foxtodd fox Scaling Testing via Automation AND Freeing The Testers To Test How to architect a scaling test automation solution that provides meaningful and actionable feedback to the entire team AND how this solution will empower and free manual testers to go and be amazing in their explorations. Two Main Points:

  1. A practical and proven approach to architecting a test automation solution that scales. This will be a high level approach to assessing a given software application/system (or systems) and how to architect automation solutions that provide meaningful and actionable feedback to the entire team. I will walk folks through real examples from a variety of domains.
  2. Incorporating manual/exploratory testing as “another feedback loop” in this architecture. I will provide real examples (from real teams) of how this works.

This presentation is for you if:

  • You need test automation
  • You need Continuous Integration (and maybe Continuous Deployment)
  • You need fewer automation tests & faster feedback loops
  • You need spec driven testing
  • You need more time to do exploratory testing
  • You need more information to convince others that you need this stuff

Who this presentation is for?

  • Software managers, leaders, and architects – people who are trying to make these decisions.
  • Automation engineers who are perplexed by ballooning test suites, perplexed by communicating test results, and feel like outliers in the the SDLC.
  • Manual Testers who fear automation and/or are trying to find their place within an organization that is moving towards automation.
Dmitry Sharkovdmitry sharkov WE are Doing it WrongAs companies mature their software development practices, automated acceptance-level testing is becoming more commonplace. In particular, Cucumber and its Gherkin-based equivalents are enjoying widespread use. Through observing and facilitating the adoption and implementation of Cucumber test suites, I have found ways in which the technology has helped teams greatly, but I have also found ways in which it hindered them. I realized that Cucumber and its kin are appropriate tools in fewer situations than the ones in which they are currently employed. In other words, many teams that use such frameworks need to reevaluate whether they are right for the job, and perhaps replace them. I invite all involved in automated acceptance testing to attend as I try to build a compelling case for this notion.