HomeNewsCall for PapersConference ProgramKeynotes
Program CommitteeRegistrationOrganizersSupporting OrganizationsSponsors and ExhibitorsVisitorsLocationHotelsContactSEETEST 2008



Sigrid Eldh
Ericsson AB

The core of testing is creating the test cases. How we actually create them, define them and design them is another matter. Important highlights on what to look for when creating test cases will be demonstrated. We will also show how to improve your current set of test cases, key considerations for selecting regression tests, and methods to challenge test to the core. Test Automation is an important part of efficient test and we will discuss test automation in relation to Test Design.

Audience: Testers - Some testing experience and basic computer skills, complete novices might have problems

Lisa Crispin
ePlan Services Inc.

Software quality has many dimensions, so we must be ready with different testing approaches. We test to find defects, ensure system reliability, check that the system is easy to use, verify that it’s secure, and much more. How do you know the different types of tests you need? How do you know when you're “done” testing? Lisa Crispin shows you how to use the four categories of the Agile Testing Quadrants method to make sure your team has covered all the bases—programmer tests (test-driven development); customer tests that help the team meet the users' requirements; business-facing tests that critique the product's behavior and find the important bugs; and technology-facing tests that examine non-functional qualities such as performance, load, scalability, reliability, and security. With Agile Testing Quadrants, you and your team will be ready to cover all the bases—no matter what testing challenges the project throws at you.

Audience: Testers, QA professionals, testing/QA managers, development managers, project managers, anyone with an interest in software testing activities. The tutorial assumes participants will have some level of basic testing knowledge, but knowledge of agile development is not required.

Mieke Gevers

Load & performance currently belongs to the top ten on the list of most critical aspects of a company its credibility, either towards the internal productivity or even the external visibility of the company via websites. But what does “Load & Performance” mean for the different parties during the life-cycle the application and how effective can we measure them?

The most nagging questions: “How well will our servers cope with high volume of users? Did the design of our back-end architecture meet the “real world” its expectations? How our end-users and customers use our systems?” To provide founded answers instead of guessing the probable outcome of these questions, a well planned and controlled Load & Performance test is needed.

This half day tutorial will get you acquainted with the used terminology and aspects of Load & Performance testing; giving you a first insight into the differed process stages needed to setup successful the load test. We will touch the aspect of information, which is requested at meetings concerning the design and architecture of a load test. Also we will talk about the ways of implementation, testing aspects & the use of measurements.

Tips regarding the load test automations, how to improve setting a stage for a load test as well as an insight on what needs to be modify scripts will be provided during the sessions.

Audience: Software engineers, quality assurance professionals, System testers/designers/tuners, and project leaders who are involved in systems testing can benefit from this course. A working knowledge of system testing and quality assurance fundamentals is assumed, but no specific technical backgrounds required.

Michiel Vroon
The Netherlands

As a test manager you constantly have to deal with change. A good test plan gives directions to deal with these demands. But the test manager needs more instruments to deal with the daily practice of running a test project.

In this tutorial you will learn several of these instruments. Explicit attention is given to the application of the instruments in daily practice. For instance, using test design techniques is a standard best practice, but what to do if there is no functional design? And what to do if our carefully defined test strategy turns out wrong? The instruments presented are derived from the test method TMap. In 2007 the completely revised test method TMap® was published in a book with the appropriate title “TMap® Next”.

In this tutorial you will get the total overview of the (revised) method, focusing on the essentials, the highlights and the changes in this "Next" version. Throughout the tutorial you will participate in discussions and cases.

Audience: Test Managers, Senior Testers

Alessandro Collino
Onion S.p.A

The most common accepted definition for Agile Testing is that it’s a practice that adheres to the “Agile Manifesto”, treating the development team as the customer of testing and used for projects using agile methodologies.

While Agile is a methodology that was created from a development point of view, testing was not ignored. The main focus, however, was placed on unit testing and exploratory testing using the assembled team. The idea of Agile Testing is that testers are able to make sure customers get what they need; they look at the “big picture” and work to ensure the best experience for the user. Professional testers can help agile developers to deliver what stakeholders want.

Actually the core of Agile Testing can be summarized as above (obviously with some variants), but this practice is still evolving and being actively discussed on mailing lists.

Audience: The tutorial is addressed mainly to “traditional” testers that want to become a “new” Agile Tester, meaning a tester that is introduced for the first time in an agile project, but more in general also to Test Managers, Product Owners, Scrum Masters and all the stakeholders that want really to know how to enforce their teams with true Agile Testers. It can be also of interest for Agile Testers that want to check and discuss the new practices of Agile Testing and the possible scenarios of this important practice.

Vipul Kocher
Pure Testing

This tutorial presents an Extension of Noun and Verb Technique.

Most of the structured test design techniques are useful when detailed requirements are available. Even with detailed requirements, the existing test design techniques leave many holes some of which are covered by ad-hoc or exploratory testing and other experience based techniques.

Extension to noun and verb technique can help create test cases even when requirements are sketchy. This technique can help create test cases of varying complexity including many test cases which no existing test design technique would have covered. The technique allows creation of scenario based tests as well as individual feature/field validation tests.

The technique has successfully been used on various projects with great results.

Audience: Test Engineers, Test Managers, Technical Focus



SEETEST 2009 Call for Papers announced soon
Deadline for submitting papers will be end of January 2009