Our FIRST Conference

SIGIST Sweden #1 2016-11-22

Time: 9:00-16:30

Place: Royal Viking Hotel, Vasagatan 1, Stockholm

 

Jörgen Damberg, Claremont

During my years in testing I’ve seen a lot of really good and experienced testers loosing track of why they do what they do. They are so focused on doing their daily work as efficiently as possible so they sometimes sub-optimize their work. I’m here to remind you about what quality is, how you can measure your success, and talk about some of the ways to get really efficient in testing – for example through automation of test environments management and test data management.

Jörgen is a well-known Software testing specialist. He has worked as a contractor in software testing issues with a history of working in more than 50 different projects as a testing specialist. He has spoken in many national and international conferences, amongst them NFI and Eurostar.

 

 

Rikard Edgren, Nordic Medtest

Rikard´s Super-Good Testing Practices

 After 18 years of software testing, I haven’t tried all testing methods, but most of them. I have tested, and advised, in many different situations, and after having learnt my lessons, I find myself using some activities very often.

It was years ago I didn’t use thetesteye’s quality characteristics on a project, but not before I let the customers use their own words.

Whenever possible I create an SFDIPOT model a la Bach, sometimes fast for strategy thinking, and sometimes thorough when generating test ideas.

I think about reporting before planning, to be sure I hit information objectives appropriately; and I can surprisingly often work fast with one-liner test ideas and bugs.

I love my models, but others’ are more efficient to communicate; and together with being open to serendipity, these are my current super-good practices.

 I will share my ways of using these in different ways; hoping they might be useful in some way for you as well.

 

Rikard Edgren has been testing since 1998 and sees himself as a context-driven, humanistic and technical tester, enjoying the dynamics between people/machines, objective/subjective, whole/details.

After a couple of years with Microsoft’s localized products, he spent 11 years with Spotfire, producer of interactive data visualization products. The learnings resulted in the free e-book The Little Black Book on Test Design.

Since 2011 he has been as a test consultant also doing testing education at companies and higher vocational studies programs, with a slight preference towards exploratory testing and test strategy.

He is a regular at national and international conferences, with seven appeareances at EuroSTAR (two of those as program committe member.) Member of the think-tank The Test Eye, author of Den Lilla Svarta om Teststrategi (in Swedish), co-author of Software Quality Characteristics, and co-organizer of SWET, Swedish Workshop on Exloratory Testing.

 

 

Andy Redwood, Redwood Associates

Quick wins in Testing that actually work

 As a senior test manager I don’t just have a responsibility to prove or disprove the changes or attempt to provide evidence of quality, although these are important. I also have to maximise services from the available budget and look for savings and efficiencies.

In reality I’m trying to achieve all of these objectives at the same time and have had some wins on small quite niche small pieces of work and also when creating economies of scale across life-cycle changes to policies or working practices.

I will share some of my experiences large and small and explain the enablers and the constraints and provide some indication (within the confidentiality agreements) of the value of these initiatives.

 

Andy’s is a senior testing practitioner managing test teams and test projects within an Investment Bank. He’s been a Test Specialist for nearly 30 years.

Andy has a personal industry profile and is a regular public speaker at international conferences. He was Chair of the UK ISEB International standards Panel in 2003/4, the UK representative to the International Board in 2003. In 2004 he founded the ISEB UK Executive Committee at the request of David Clarke, the Chief Executive of the British Computer Society.

Andy was awarded the EuroSTAR Award for outstanding contribution to the Software Testing Industry in Europe, in December 2005, following a previous nomination in 2003.

 

 

James Bach, Satisfice

Test Cases are Not Testing: Toward a Performance Culture

Testing means evaluating a product by learning about it through experimentation. This is a dynamic, exploratory process. Although we might script parts of it, and even reduce some of it to programmatic fact checks, testing itself is a live performance. In fact, all technical work is a live performance. Programming, managing, designing… it’s all a performance.

Meanwhile, for many years, some managers have dreamed of making technical work into a factory activity. That would require thinking of testing, for instance, as being encoded in artifacts such as “test cases.” The primary aim of that effort is to turn testing into a commodity and to devalue testers.

To fight back we need to become better at explaining “performance culture” and better at arguing for what can and cannot be done with a script.

 I started in this business as a programmer. I like programming. But I find the problems of software quality analysis and improvement more interesting than those of software production. For me, there’s something very compelling about the question “How do I know my work is good?” Indeed, how do I know anything is good? What does good mean? That’s why I got into SQA, in 1987.

 Today, I work with project teams and individual engineers to help them plan SQA, change control, and testing processes that allow them to understand and control the risks of product failure. I also assist in product risk analysis, test design, and in the design and implementation of computer-supported testing. Most of my experience is with market-driven Silicon Valley software companies like Apple Computer and Borland, so the techniques I’ve gathered and developed are designed for use under conditions of compressed schedules, high rates of change, component-based technology and poor specification.