automated testing

What's the Right Level of Testing?

room: Grand Ballroom D North — time: Wednesday 16:45-17:30
Level: Introductory

I’ve been on teams with way too little and (heresy) way too much testing. There have been lots of talks about how you should test more, but I’m going to dare to talk about when you should test less. Too much testing can lead to backlash, gridlock, morale problems, and poor velocity. Of course lack of testing can lead to bad design, gridlock, morale problems, and poor velocity. The level of testing a team can support depends on many factors including: team size, developer buy in, managerial approval, company size, IT support, and testing experience.

Large scale continuous integration

Level: Practicing

Increase Productivity With Large Scale Continuous Integration Iteratively: Reduce Feedback Cycle From Weeks To 100 Minutes

Using iterative development – create an continuous integration environment using open source and commercial tooling for hundreds of developers
From migration to new environment – the tools and process lessons learned
Effects seen in product development – real life experience after 18 months in production

XUnit Test Patterns and Smells; Improving Test Code Through Refactoring

room: Grand Ballroom C North — time: Monday 14:00-14:45, Monday 14:45-15:30
Level: Practicing

XUnit is the generic name given to the family of tools/frameworks used by developers when developing automated unit tests. JUnit, NUnit, MsTest and CppUnit are some of the better known members of the family. High quality automated unit tests are one of the key development practices that enable incremental development and delivery of software. This tutorial provides the participants with a vocabulary of smells and patterns with which to reason about the quality of their test code and a set of reusable test code design patterns that can be used to eliminate the smells.

Enabling Agile Testing through Continuous Integration

room: Grand Ballroom D North — time: Wednesday 16:00-16:45
Level: Introductory

A Continuous Integration system is often considered one of the key elements involved in supporting an agile software development and testing environment. As a traditional software tester transitioning to agile environment, it became clear that we would needed several changes to make the transition to agile testing possible. This experience report discusses a continuous integration implementation I led last year. The initial motivations, technical specifics of the implementation, perceived benefits to the team, and retrospective results are all discussed.

Applying modern software development techniques to automating the web UI

room: Regency D — time: Thursday 11:00-11:45
Level: Practicing

In today’s Agile development environment, UI testing is still very much done the old way. We still see long scripts that are easily broken and impossible to maintain. By applying modern software development techniques like test first development, refactoring, and pair programming we can seek to make better tests that are less fragile and more likely to discover defects in code. In this session we will demonstrate the techniques listed above and discuss how they can be applied to UI testing. The demonstration will use a combination of fitnesse and SWAT (an open source web UI testing tool).

Syndicate content