Præsentationer 2019

Vi vil løbende offentliggøre præsentationerne på årets konference på denne side.
Der tages forbehold for ændringer.
Tilbage til Hovedsiden


Accepttest i den agile verden

IT afdelinger buldrer derudaf på de agile toge. Vi skal levere hurtigere til produktion og vi som industri har først nu for alvor fået agil udvikling ind under huden. Mange af de store virksomheder i dag er gået over til agil udvikling og begynder at kunne høste fordelene af det hårde arbejde. Grundpræmissen om at kvalitet og test er en indbygget del i udviklingen skal stadig motioneres lidt, men selv den del er i positiv udvikling. De eneste som måske ikke helt er kommet ombord på toget endnu er kunderne, de står stadig på perronen og spørger sig selv hvornår toget stopper, så de kan komme med.

I al min tid i test, har accepttest ikke været det der er blevet prioriteret højest på listen – det har været den der lille testfase til sidst i projektet der skulle overstås, det er mere en formalitet end en reel test. Fejlen har ligget på begge sider af bordet – udviklingen anerkender ikke altid vigtigheden og kunderne har ikke de fornødne redskaber til at foretage testen eller tiden for den sags skyld.
I agil udvikling er det mere end legitimt at inddrage kunderne tidligt i processen, det er snarere et krav at user stories bliver godkendt umiddelbart efter udviklingen er færdig, så den kan komme i produktion. Men selvom IT er i gang med den agile transformation har kundernes forudsætninger og indstilling ikke nødvendigvis ændret sig. De er hverken klædt bedre på til at foretage accepttesten og de har heller ikke fået mere tid.

Hvordan får man kunden ombord på toget? I min præsentation vil jeg komme med forslag til hvordan og hvornår kunden skal inddrages.

Jeg vil komme ind på følgende emner:
– Hvad siger SAFe egentlig om accepttest
– Vigtigheden af gode acceptkriterier
– Accepttest af features og brugertest af stories
– Udvælgelse af testdesignteknikker til accepttest og brugertest
– Planlægningen af testen der involverer kunden
– Rollebeskrivelse

Præsentationen er baseret på mine erfaringer med accepttest i både traditionelle og agile udviklingsprojekter.
Navn: Bettina Lysell Faldborg, Virksomhed: Q Nation
Præsentationen er på dansk.
Tilbage til toppen.

Automation to the rescue! Testing a 100.000 camera video system

Milestone is the world leading software manufacturer for Video Management Systems. We are working in the security industry and reliable systems are essential to our customers.
Milestone started its journey on moving from 100% manual testing to almost exclusively automated testing in 2012. By 2015 we had laid the foundation of the current framework.
In 2016 we got hit by an number of customer cases related to scalability and performance. This hurt us a lot. We needed to improve.
The presentation will explain our situation back then and how we got to where we are now with a fully automated large scale test suite, that daily ensures our software quality and scalability.
Large Scale Testing is especially complicated because the setups by nature are very complicated:
– How do you test a system with 100.000 cameras
– How do you test a system distributed over 1.000 servers
– How do you test a system with more than 1.000 different users
It is important to understand that this is NOT a online system where we can apply patches, load balance, and can control the hardware. These systems are installed locally at the costumers sites, and with whatever hardware they choose. This means that we need to be very innovative in our approach when designing tests and setting up the systems.
Throughout the presentation I will show some of the problems that we encountered on our journey and how we solved or worked around them.
Navn: Rune Holstvig, Virksomhed: Milestone System A/S
Presentation is in English.
Tilbage til toppen.

Finding and removing bugs: Can history teach us anything?

Story: Our research group has engaged with two flagship open source projects: the Linux kernel and in the Robot Operating System (ROS). We wanted to help these projects to find bugs faster and cheaper. In order to understand where the problems are, we have carefully analyzed the major quality issues in these systems by studying historical bug reports and historical fixes.

Problem: Source code repositories and issue tracking systems provide a wealth of information about the quality problems in your system. But it is not clear how to exploit this knowledge. While many problems are and could be addressed by existing tools, many are highly system specific, and no general tools exist for them.

First, we had to reproduce a lot of bugs on historical releases of software. We used a container setup for testing and experimenting with multiple releases of the same system simultaneously.

Second, we learnt that many standard problems can be detected automatically with low-level existing solutions: fuzzing and sanitizing.

Third, we learnt that many project-specific problems are simple. They can be detected by custom very light-weight code scanners. We learn about a bug one place, but once we script a custom scanner, we can find similar problems elsewhere in the same system.

In the presentation Andrzej Wasowski will discuss how Docker allows setting up such test environments cheaply (for instance to reproduce a bug in a particular customer’s version of the system). You will see examples of how to use fuzzing, sanitizing and custom scanners. To conclude, Andrzej will show a glimpse into the future, discussing how AI could be used to exploit the history of the system to prevent future problems.
Navn: Andrzej Wasowski, Virksomhed: IT University of Copenhagen
Presentation is in English.
Tilbage til toppen.

From Quality Assurance to Quality Assistance

Quality Assistance is the trendy buzzword for modern software quality processes, where the whole organisation takes a proactive role in activities traditionally reserved for quality assurance specialists. Gojko will present proven techniques for coaching, facilitating and influencing software teams to adopt a quality assistance model, along with adoption tips and potential pitfalls distilled from experiences of other organisations.
Navn: Gojko Adzic, Virksomhed: Neuri Consulting LLP
Presentation is in English.
Tilbage til toppen.

Is Synthetic Test Data the only Road to Rome?

Due to compliance reasons, GDPR, we are all thinking about our test data! We can’t use production data anymore, but what test data can be used?!?

Maarten has experience with two different approaches to create GDPR compliant test data without compromising quality. However it is not a trivial task. What are the pros and cons of test data masking versus test data generation? How do you select the best method for your project? During the presentation Maarten will discuss the challenges of test data masking versus synthetic test data generation using real-life examples.

An unexpected benefit has also emerged from Maarten’s work with test data. Maarten has experienced that projects are able to improve the software quality by analysing when, where and how to use masked or synthetically generated test data!
Navn: Maarten Urbach, Virksomhed: DATPROF
Presentation is in English.
Tilbage til toppen.

Rethink the architecture & design of your Continuous Delivery pipelines

Continuous integration and delivery has come a long way in the past few years. Not long ago, it was a distant dream for most organisations. Technical decision makers talked about it, but it was not clear to anyone in terms of what it is and how to get started. What we now take for granted because of the prevalence of CI/CD in modern tech companies would have been considered impossible only a decade ago.

This presentation will start with a general introduction to CI/CD pipelines and processes, what is the basis of these processes, why were they started in the first place, what are we trying to achieve from them and how these processes have evolved over the years.

It is a constant struggle in organisations to setup a robust, reliable, functional and fast CI/CD pipeline that takes your work to deployment in the most reliable fashion and in the minimum amount of time.

This presentation intends to reflect on some of the vital technical design principals that should be considered/followed during the implementation of the CI/CD pipelines. The purpose is to motivate the teams to take a moment and reflect on their Continuous Delivery/Deployment pipelines architecture with the sole purpose of evaluating and determining the steps that can be taken to improve it. The presentation will discuss in detail multiple common obstructions and hurdles that can exist in CI/CD pipeline. For example security, tooling, visualisation etc

Discussing these design principals in detail and highlighting their pros and cons can assist teams in establishing pipelines that deploy/release more frequently and robustly, they will help the teams to work in smaller batches and build quality in software through automation

There are challenges ahead and the industry is going through a phase shift in terms of faster release cycles and better product quality, but on the bright side, things are moving fast and in most cases in the right direction. As long as people and organisations continue to challenge the status quo and don’t forget the tedious six-month long release cycles that started this phase shift in the first place, I have no doubt in my mind that mature and reliable CI/CD processes will be a standard in the future.
Navn: Ambreen Sheikh, Virksomhed: Diabol AB
Presentation is in English.
Tilbage til toppen.

Politiets succes med pairwise testing giver tillid til bødeberegninger

Politiet er lige nu midt i en transformationsproces, hvor betjentenes brug af bl.a. blanketter og radioopkald i stort omfang erstattes af smartphone-apps, hvilket giver både større kvalitet og effektivitet i sagsbehandlingen. Ét eksempel herpå er Bødeappen, der anvendes til færdselsforseelser.

En central komponent er Bødeberegner, der implementerer kompleksiteten af kombinationerne af færdselsforseelser og var derfor planlagt anvendt med en efterfølgende manuel godkendelse. Ved anvendelse af den klassiske testteknik Pairwise Testing genererer vi nu 1000-vis af testcases til Bødeberegner, og testdybden kan let øges til triplets/quadruples/… inkl. negative testcases, hvis det er ønskeligt. Vha. et ’orakel’ kontrolberegnes den forventede bøde og antal klip i kørekortet. SoapUI anvendes til at afvikle de genererede testcases samt sammenligne Bødeberegners resultat med det forventede resultat.

Efter ovenstående testforløb endte det med, at National Færdsel selv foreslog at implementere “automatiseret” bødeberegning for færdselsforseelser, da testteknikken gav eksperterne tilstrækkelig stor tillid til dens korrekthed.
Navn: Søren Lynggaard, Virksomhed: Rigspolitiet
Præsentationen er på dansk.
Tilbage til toppen.

Risk-based test, are you talking the talk or walking the walk?

Whether your project is developing in a traditional way or in working in an agile context, a common view of product risks and how they should be addressed is crucial for an effective and well-founded test. The use of the term “risk-based test” is often heard when we discuss how we test in our projects, but if you as a tester or test manager took a close look at your project – is it then really product risks that control the decisions about testing? How is the information on product risks used in your project, besides documenting them in the test strategy? do you use it specifically when developing and running tests? And are you following up on the mitigation of them? In this presentation, Gitte Ottosen will introduce various approaches to product risk analysis, with a strong focus on the conversation / discussion process and the role of the various team members / stakeholders in identifying and classifying product risks as a team effort. How do we maintain product risks to ensure that they are actually understood and used as a basis for the test in the project. How to get the right communication in place, so it is applicable to the team. But most important of all – how do we actively use it when planning, specifying, developing and executing tests. In a risk-based approach, the product risk analysis should be the basis for your test cases – not just something in a test strategy document. And remember; Product risk ownership is common, it is the whole team’s responsibility to understand product risks and mitigate them
Navn: Gitte Ottosen, Virksomhed: Capgemini
Presentation is in English.
Tilbage til toppen.

Slotsholmmetoden – værktøjet til skarpe beslutningsoplæg

Slotsholmmetoden er en samlet pakke af regler for effektiv produktion af notater. Reglerne giver tilsammen løsninger på en lang række problemstillinger, der til alle tider har rejst sig for notatproducerende medarbejdere. Organisationer, der bruger metoden konsekvent, vil kunne høste gevinster på tre områder: Det bliver nemmere at være bestiller, skribent og beslutningstager.

Det kan siges helt enkelt: For at få hvad-som-helst til at virke i praksis skal både bestiller og tester forstå, hvad der bliver efterspurgt. Dårlig skriftlig kommunikation giver anledning til uhyre mængder af spildtid, misforståelser og fejl. Netop det kan der rettes op på, hvis man går metodisk til værks, når man kommunikerer med hinanden. Metoden kan i høj grad bruges i kommunikationen mellem bestillere og testere i en hvilken som helst organisation.

Metodens elementer er grundigt gennemgået i bogen SLOTSHOLMMETODEN – billede af denne er vedhæftet. Metodens elementer indgår i pyramidefiguren, der ligeledes er vedhæftet.

Et hint om et af de centrale redskaber er, at man kræver bestillinger stillet som svar på de tre centrale spørgsmål – hver gang. Spørgsmålene er: Hvad er bestillers ærinde (hvad er det man vil have belyst)? På hvilken måde (eller: For hvad) er det vigtigt? Og: Hvad skal der ske som konsekvens af bestillingen (skal nogen vide, beslutte eller handle?

En lidt mere fyldig, men fortsat kort, gennemgang af metoden kan læses i pdf’en: ‘Slotsholmmetoden – kort fortalt’, som er her
Navn: Hans Jorgen Nielsen, Virksomhed: Slotsholm Aps
Præsentationen er på dansk.
Tilbage til toppen.

The Hidden Requirements: Exploring Emotions with Placebos

Traditionally, software development has focused on various functional and non-functional requirements (things a system should be or do). While this is important, there has been a lack of focus on emotional requirements (feelings that a system should induce). Why is this important?
Because the way we feel about software is important and should be considered!
A bold claim? Perhaps. And, as with any claim, it should be supported with evidence.
In this presentation, I stress the importance of emotional requirements and support the claim by providing relevant facts, opinions, statistics, quotations, examples, hypotheticals, and more.
Once I’ve sufficiently supported the claim, I offer a few practical methods by which to obtain, create, and assess emotional requirements.
Finally, I use placebos as lens through which to view software and gain insight into emotional requirements.
Join me to for a thoughtful and thorough exploration of The Hidden Requirements!
Navn: Damian Synadinos, Virksomhed:
Presentation is in English.
Tilbage til toppen.



Improv(e) Your Testing!

Improvisational comedy—sometimes called improv—is a form of theater in which the performance is created in the moment. Successful improv involves learning and using a variety of skills and techniques which allow performers to quickly adapt to a constantly changing environment and new information. Now reread the previous sentence, but replace the word improv with testing.

In many ways, improv is a great analogy for testing. As both an experienced improviser and tester, Damian Synadinos presents some of the many similarities between improv and testing. Each improv tip and trick is thoroughly described and demonstrated with help from the audience. Damian then explains and shows how the very same idea can be applied in a testing context. Using creative metaphors and critical analysis, old ideas about testing are reframed in novel and notable ways.

Whether novice or experienced, you are sure to laugh, learn, and leave with ways to help improv(e) your testing!
Navn: Damian Synadinos, Virksomhed:
Workshop is in English.
Tilbage til toppen.

Winning big with Specification by Example

Specification by example (SBE) is a collaborative approach to defining requirements and tests for based on capturing realistic examples instead of abstract statements. It is the corner-stone of any successful requirements and testing and requirements strategy with agile and lean processes, such as Scrum, Extreme Programming and Kanban.

This half-day workshop will motivate and inform you about behaviour driven development and specification by example. You will get a good foundation for further research and adopt the chosen practice faster by avoiding common problems.

Key learning points

This seminar is based on Gojko Adzic’s books Specification by Example and Bridging the Communication Gap. The key learning objectives for the participants are:
– key benefits that successful teams get from specification by example
– key principles underlying successful process implementations: deriving scope from goals, specifying collaboratively, illustrating using examples, refining -specifications, automating validation without changing specifications, validating frequently and evolving a living documentation system
– key practices to support the principles, and how teams use them in different contexts, from investment banking to web development, from small collocated teams to distributed groups of teams
– how specification by example fits into Kanban/Scrum
– getting started – key steps to take and key things to watch out for

Feedback from previous participants:

Great value achieved, specifications with examples and executable specifications will become an important addition to our agile processes. I have already managed to inspire our Test Manager and key team member of our teams
— Martin Fredriksson, Technical Architect, Centiro Solutions AB

It is a good intro to the topic and it is well worth attending. It gives a lot of ‘aha’ thoughts
— Stefan Schwartz, Software Configuration Manager, ICA AB

Good training to learn about improving requirements process
— Jan Van Reusel, Software Factory Manager, Cegeka

Supports formal Agile training brilliantly as it gives you insight to real, practical techniques and examples that will help facilitate true collaboration and as a result eliminate waste and raise quality
— Jenny Martin, Systems Delivery Manager, Groupe Aeroplan

Highly recommend it. Definitely takes quality techniques to a new level
— Drew Preston, Development Services Manager, G3 Global

So much challenging and interesting information on eliminating waste in software
development. Everyone should join
— Morgan Johnston, Agile Lead/Developer, Digiterre

It was very helpful to start questioning myself on better ways to get requirements
— Benjamin Arroyo, Software Consultant, Bespokia Ltd

Thought provoking, inspiring, collaborative. Don’t think about it, just go
— Chris Carney, Quality Engineering, UBS
Navn: Gojko Adzic, Virksomhed: Neuri Consulting LLP
Workshop is in English.
Tilbage til toppen.

DSTB på LinkedIn


Du kan tilmelde dig den åbne gruppe her

DSTB på Twitter

Du kan følge os på @dstb_dk og konferencen på #DSTBKonf.Twitter_logo_blue

Digital Quality and Testing Meetup

Are you interested in quality and testing? Then you can meet like-minded people in our group on Meetup called: Digital Quality and Testing Meetup in Denmark.

Click the link to join the group:

You can read more about the group here: