Præsentationer 2018

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

Better Safe Than Sorry

Business agility is key as disruption of sectors and industries becomes the new normal. Earlier IT was a means to faster and cheaper production of products and services. Today IT is an integrated part of most products and services. Therefore becoming agile at scale is vital but at the same time very challenging for most large organisations.
Scaled Agile Framework is one of the most popular frameworks used by enterprises to become more agile not just on team level but on all levels.
SAFe as a framework describes many good practices to build-in quality, but when it comes to the actual implementation in large organisations there is a need for better guidance for people in test departments who work like testers, test analysts, test coordinators, test managers to name a few.
Before we let others decide how the future of testing will be let’s disrupt it ourselves.
In this talk Mette will share some of her experiences implementing SAFe and the new diversity we already face in our testing profession.
Navn: Mette Bruhn-Pedersen, Virksomhed: Safe Journey
Presentation is in English.
Tilbage til toppen.

Cartoonify Your Risks

Story / Problem:
In Ørsted (former Dong Energy), the Test Management (TM) team has decided to focus on implementing an aligned Risk-based approach in all projects within the company and thereby an early involvement during analysis- and planning phase. The reason is, that the team often experience late assignment to projects regarding test planning and execution.

Implementation / Challenge:
I prepared a power point presentation and had my first ‘pilot-run’ in presenting a Product Risk Analysis approach for a project. Firstly, I spend 10-15 minutes explaining the concept, trying to make them think in new ways and methods as we were used to do. I gave them the task to give me examples on risk definitions in their product and told them to think out of the box – there were complete silence in the room… One project member asked me: “How can you expect us to think out of the box, when all you do is showing us excel sheets and matrix’!?”

Solution / Outcome:
I realized that I had to think out of the box myself before I could tell others to do the same. Therefore, I went a whole new way and created a presentation by using cartoons, explaining the journey we were about to travel and the expected outcome (using a car from it is build and until it is driving on the road). I was very much out of my comfort zone first time a project were exposed to this presentation form; how can very analytical people relate to a bunch of cartoons? But they embraced this method immediately and I am also introducing the use of Mind Maps when they must brainstorm regarding potential risks in the product.

Lessons learned are collected and the presentation is continuously improved. The outcome of this approach is that the entire TM team now actually receive early test involvement in the projects and there is an extensively focus on the actual value we bring in the projects. The mindset has shifted so the TM team is now actually being involved during the analysis phase and hereby contributing with quality improvement in an earlier stage of the project.
Navn: Maria Møller, Virksomhed: Ørsted
Presentation is in English.
Tilbage til toppen.

Den agile tester – proaktiv brug af testdesignteknikker til behovsafklaring

I takt med øget kompleksitet og det øgede antal leverancer, har vi et stort behov for at bygge kvalitet ind tidligt i vores udviklingslivscyklus. Vi skal forstå løsningen og være i stand til at kommunikere på tværs af forretning og IT.

Som medlem af et agilt team er testerens rolle anderledes – og bredere. Som en integreret del af et agile team er du involveret fra første dag, og du har derfor mulighed for at bidrage til at støtte dit team i at forstå forretningens behov, og dermed at hjælpe forretningen til at beskrive deres behov. Hvor den klassiske user story fokuserer på en helt overordnet beskrivelse af et behov og et mål, og acceptkriterierne primært fokuserer på konkrete funktionaliteter og non-funktionelle aspekter som skal implementeres, så kan du med din testværktøjskasse tage dette et skridt videre. Du kan hjælpe med at skabe et overblik – eksempelvis hvordan de forskellige User Stories er relateret til hinanden i en proces og opnå en fælles forståelse af hvad software skal bruges til; på en letdokumenteret og visuel måde som skaber værdi for team og bruger.

Her kan forskellige modeller, som vi kender fra vores testdesignteknikker være et fantastisk værktøj. I stedet for at bruge testdesign i isolation som et værktøj til design af testcases, så begynd i stedet at se dem som et modelleringsværktøj til behovsafklaring – at du kan bruge det som input til en effektiv test efterfølgende, er jo bare en ekstra bonus.

I denne præsentation vil Jakob Frisenvang introducere dig til en proaktiv brug af et par af de allermest velegnede teknikker til visualisering og kommunikation af brugerens arbejdsgange og behov, så du efterfølgende kan skabe endnu mere værdi for dit team og dit projekt.
Navn: Jakob Frisenvang, Virksomhed: Cap Gemini Sogeti
Præsentationen er på dansk.
Tilbage til toppen.

Den STORE bogstavstest

Hør om, hvorfor software-testen har afgørende juridisk betydning og hvorfor software-testerne bør kende indholdet i udviklingskontrakten.
Oplægget vil illustrere sammenhængen mellem den juridiske aftale og de konkrete test-aktiviteter, herunder planlægningen af software-testen.
Samtidig vil der med udgangspunkt i konkrete ”real-life” retssager blive givet eksempler på, hvordan software-testen og dokumentation heraf kan være afgørende for en virksomheds juridiske stilling i en retssag.
Navn: Kim G. Hansen, Virksomhed: Integra Advokater
Navn: Majbritt Alemany, Virksomhed: Integra Advokater
Præsentationen er på dansk.
Tilbage til toppen.

Det er aldrig for tidligt at teste

Tidlig Test, Early Feedback, Shift Left …….
Kært barn har mange navne. Kønne børn har flere. Tidlig validering og feedback er et bedårende barn.
Der tales overalt om, at vi gerne vil af med den plagsomme testbyrde, der vanligt hober sig op, når vi nærmer os mållinjen, og som ydermere har det med at vokse sig større og grimmere, jo tættere vi kommer derpå.

Det skal vi væk fra.
Oven i hatten har de fleste slået rødder i den agile transformation – med fokus på de mindre men hyppigere releases – der i sagens natur sætter sine begrænsninger for, hvor meget test vi kan tænke ind i de sidste dage af et sprint eller som rosinen i release-enden.

Så ingen vej tilbage. Længere frem i bussen med test.
Automatisering har været forsøgt som den ultimative sandhed, men har langtfra været forløsende.

Så hvad gør vi?
Vi må sadle om og komme væk fra kun at bestræbe os på at være gode til at finde fejl – for i stedet at blive gode til ikke at lave dem. Det er nemlig aldrig for tidligt at teste.

Jeg har inviteret tre forskellige bud (personer) med på scenen, og vi vil sammen dække en række praktiske vinkler på, hvordan Test kan og bør tænkes ind fra første færd – og derved blive til proaktiv adfærd mere end reaktiv risiko minimering.

Vi behandler spørgsmål som:
Hvor tidlig kan man teste? Kan man teste en idé? En vision? En strategi? Et design? og hvordan gør man så det?
Hvordan påvirker det mig og min rolle som Tester, at skulle være proaktiv?
Kan teknologien hjælpe os?
Hvordan får vi så kunden med? Hvordan sikrer vi, at vi ikke taber dem af syne undervejs?
Navn: Claus Venlov, Virksomhed: Testlab.io
Navn: Lisbeth Hylke Thomsen, Virksomhed: TestHuset.dk
Navn: Roland Møller, Virksomhed: TestHuset.dk
Navn: Søren Wassard, Virksomhed: TestHuset.dk
Præsentationen er på dansk.
Tilbage til toppen.

Dirty Little Secrets from ISTQB

“Got your attention, didn’t I?”
“Sorry, in this presentation there won’t be told any dirty secrets from the inside of ISTQB, no secrets will be told at all, actually. I signed a NDA when I joined up and the people there are my collegues and friends.”
However, what I will tell about is how ISTQB operate, how you and we in DSTB can influence the work being done in ISTQB, and as much about the future pipeline as I’m allowed to tell ;)”
Navn: Klaus Skafte, Virksomhed: DSTB
Presentation is in English.
Tilbage til toppen.

Evolving Role of Software Testers in the Era of DevOps, IoT, AI and UX

The world is changing rapidly, technology advances in the blink of an eye, systems are getting more and more complex, and businesses need to ‘innovate’ to remain competitive in this challenging world. This brings out the ’Software Tester 2.0′ model, which defines the evolving role of a software tester in the era of Complexity, Digitalization (IoT, AI, AR/VR), Agility and User Centricity.
In this challenging era, customer needs are also changing rapidly. Therefore, companies should change the way they think, the way they initiate and manage the change in their organizations. They need to adapt to change, focus on strategy, value and innovation. For this reason, the role of Software Tester stands at the heart of the future success for companies. For the last few decades, software testing is one of the fastest growing market instruments in the IT world, so as test automation. As more and more complex applications go into production; traditional software testing approaches failed to fulfill the needs, consequently organizations are looking for smart and easy solutions to address their testing requirements, especially in the new era of Internet of Things (IoT), Artificial Intelligence (AI) and User Experience (UX).
Baris Sarialioglu set’s out to assist software testers to carry out paradigm shifts in their mind-set about Software Testing and Software Tester’s role. He’ll help you set practical standards for the future of the software testing profession, with a special focus on User Centricity, User Experience (UX) and Usability Testing.
Navn: Baris Sarialioglu, Virksomhed: Keytorc Software Testing Services
Presentation is in English.
Tilbage til toppen.

Forget Quality

When you take a deep dive into the wondrous world of test policies, plans, strategies, approaches and charters, you encounter a lot of terminology and metrics that do not belong there: requirements coverage %, code coverage %, test execution %, number of open defects … Our ideas about when software is good enough are incorrect. Either we don’t reach the described quality level, or we put the software in production, no matter what. In short: our quality expectations are too high!
The average score on must high schools and universities is 56%.That’s why special grades are awarded: 65%: Cum Laude, 75%: Magna Cum Laude, 85% Summa Cum Laude. If our brightest minds fail in scoring more than these percentages, why do we expect them later in to score higher in their professional life? Domain knowledge, expertise, training,… will not significantly improve the quality level.
As testers, we’re always complaining about requirements and user stories. They’ve got to be SMART. But do we really want that? And what’s the impact on timing, budget and resources?
In addition, Les Hatton calculated that over the last 10 years, the defect percentage (# defects / KLOC) has remained constant. So even our code is not getting qualitatively better.
Our ideas about when software is good enough are incorrect, and our quality expectations are too high!
Are there other ways of thinking about quality? One way would be by creating a cone of quality, with its determinants being scope, the inverse of budget and the inverse of time. Another way is thinking about opportunity instead of risk. Why don’t we using Wiegers quality model, and measure quality by the opportunities we create for our customers? Or we could use the Kano model, with its dissatisfiers, sattisfiers and delighters, and report accordingly.
One thing is certain: our vision (as testers) on quality is different than the vision of most people. If we cannot change that, testing will remain to be seen as the main bottleneck in software development.
Navn: Michaël Pilaeten, Virksomhed: CTG
Presentation is in English.
Tilbage til toppen.

Hvordan sikrer man, at løsningen er compliant?

Virksomheder i dag bliver underlagt flere og flere områder der skal leves op til f.eks. nye love, standarder, interne politikker, best practices, non-funktionellekrav osv. Indlægget vil gennemgå nogle af de områder og principper som langt de fleste virksomheder er underlagt. En gennemgang af et rammeværk og metode der på en relativ simpel måde kan benyttes til at kravstille, kvalitetssikre og teste at løsninger er compliante.
Navn: Kenn Munk Larsen, Virksomhed: Pensam
Præsentationen er på dansk.
Tilbage til toppen.

If the users can’t use it, it doesn’t work

This talk provides a basic introduction to usability and usability testing. It also openly discusses the options and the pros and cons of usability certification (CTFL Usability Tester).

The quality of software goes far beyond the classical testing of software. Today, basic knowledge about usability is essential for software test specialists. The talk will show examples of usability problems and explain the “think-aloud” method for usability testing. It will also explain how usability testing fits into the software development cycle, and how usability is much more than cool design and clever animations. Good usability helps your users get their job done fast and comfortably.
Navn: Rolf Molich, Virksomhed: DialogDesign
Presentation is in English.
Tilbage til toppen.

Innovate with Minimal Risk

Hvordan kan vi hurtigt innovere, med minimal risiko? Kan man som tester eller kvalitetsansvarlig ’tillade’ at vi finder fejl i vores produktions miljøer?
Ja, det kan man godt.
Hvis man har det rigtige set-up.
Dual- track agile konceptet bakker netop op om denne tankegang.
Vi tester vores ideer af på brugerne, laver det absolut minimale for at lukke nye ting ud til brugerne, laver A/B split tests, samt ruller nye features langsomt ud til brugerne, fx ved at starte med at lukke op for 10% af brugerne og holde et meget vågent øje med logs, tjekke bruger reviews/uservoice, samt tæt kommunikation med brugerhenvendte kanaler som Kundeservice.
I denne præsentation vil jeg komme med eksempler på den måde vi tester nye features/produkter af på vores kunder, samt beskrive min egen rolle i vores nye set up.
Navn: Louise Thyrring Rasmussen, Virksomhed: eBay Classifieds Scandinavia A/S
Presentation is in English.
Tilbage til toppen.

Realisering af gevinster i et test- og kvalitetsperspektiv

Realiseringen af gevinster er en sort box i mange projekter. Der er et stort potentiale for at sætte realiseringen af gevinster i centrum af vores projekter med henblik på at optimere udbyttet af dem. Realiseringen af gevinster forudsætter krav og leverancer af rette kvalitet. Og derudover skal vi oftest også lykkes med ændring af adfærd samt ændrede kompetencer. I præsentationen ser vi på, hvordan styring af projektern ud fra gevinster stiller krav til og bidrager med input til kvalitetssikrings- og testaktiviteterne i projekterne.
Navn: Michael Kristiansen, Virksomhed: Implement Consulting Group
Præsentationen er på dansk.
Tilbage til toppen.

Sharpen Yourself, You Need to be Fit

As testers we often use tools to increase our productivity. But do we also remember to keep ourselves sharp?
In this presentation Klaus Olsen will talk about how you can keep yourself sharp and follow Stephen R. Covey’s habit number seven.
During his 18 years in his own company Softwaretest.dk Klaus has focused on how to sharpen the saw.
Klaus has done this through courses, certifications, everyday work with a wide range of customers, and by networking with ISTQB testers worldwide.
Navn: Klaus Olsen, Virksomhed: Softwaretest.dk
Presentation is in English.
Tilbage til toppen.

Test automation might be hard… but certainly not impossible

Based on 19+ years of experience + interest in “automated testing” by using other people’s systems and tools and creating 3 full “test execution systems” from scratch.

Several conclusions are clear in my mind and I would like to share:
* Automated tests and manual tests should not be very different in content and wording.
* The transition from “old fashion test specifications” to “fully automatic tests” don’t have to happen in one step. Consider the value of “read aloud” or “Semi-automatic tests” with auto generated reports.
* Transform knowledge from “domain users” to testcases can be automated by recording their interactions.
* And others topics…

Some of the challenges in making automated testcases could be:
* Making the testcases abstract enough including making the code/implementation readable and simple.
* Determining the correct PCOs (Point of Control and Observation).
* Automating the drivers of the PCOs – RS232/RS485/CAN/ethernet/USB, screenshot + Image recognition, OCR, REST API, key presses, SI unit measurement and stimuli etc…
* Improve generated reports without having to rerun the tests.
* And others…
When said automation might be hard we have a couple of embedded products here at DEIF where 100 % of all identified tests are automated (knowing that you will never be able to identify all meaningful tests).

Demonstrations of some of the above statements will be made during the presentation.
Navn: Flemming Futtrup, Virksomhed: DEIF A/S
Presentation is in English.
Tilbage til toppen.

Test i DevOps – myter, realiteter og udfordringer

Der kommer løbende nye udviklingsmetoder og fremgangsmåder, og som softwaretester skal man hele tiden sørge for at følge med.

En af de seneste nyskabelser er DevOps. Men der er megen diskussion om hvad DevOps er, hvordan testen skal indgå som del af DevOps miljøet. Nogle fremfører, at DevOps betyder at testere bliver overflødige – hvad er op og ned på denne diskussion. Det vil forsøgt at blive afmystificeret i dette indlæg, som også vil omfatte eksempler fra indlægsholderens hverdag.

Præsentationen vil fokusere på:
– Hvad er DevOps
– Test og testere i et DevOps miljø
– Udfordringer for test og testere i DevOps miljøet
– Fastlæggelse af teststrategien for DevOps, herunder Continuous Testing
– Fra test til QA – et nødvendigt paradigmeskift?
– Eksempler fra projekter
– Konklusion: Myter, realiteter og udfordringer for test i DevOps
Navn: Ole Chr. Hansen, Virksomhed: Q Nation A/S
Præsentationen er på dansk.
Tilbage til toppen.

Test i et ledelsesperspektiv

Den udvikling som der har været indenfor test management de sidste mange år har grundlæggende ikke forbedret produkternes kvalitet, men skab et lag af administration omkring testarbejdet som har forlænget projekterne betydeligt, som man ikke kendte til for 15-20 år siden. Det er særligt indenfor den offentlige sektor har denne udvikling været markant. Der er dog en undtagelse, nemlig anvendelsen af automatiseret tests, som brugt rigtigt kan reducere antallet af fejl i forbindelse med vedligehold og videre udvikling af systemerne.
Navn: Ivar Niels Juul, Virksomhed: KMD Business
Præsentationen er på dansk.
Tilbage til toppen.

Testledelse på kundesiden

Rollen som modpart og medspiller for leverandøren omkring test og kvalitetssikring af leverancerner. Hvad har jeg som kunde behov for fra leverandøren i projektforløbet. Hvad er på spil, når man både skal samarbejde med leverandøren, godkende leverancer og repræsentere forretningen.
Navn: Lea Dall Zilmer, Virksomhed: Nationalbanken
Præsentationen er på dansk.
Tilbage til toppen.

Why MBT 3.0 is the perfect test approach for your agile project

In this talk we present how the visual test design supported by MBT strongly helps the collaborative discussions between Business Analyst, Product Owner, Testers and even Developers to better understand the business requirements to be implemented. Then, these MBT-generated acceptance tests represent the user’s point of view and act as a form of requirements to describe how the system will function, as well as serve as a way of verifying that the system works as intended. This will help you to implement approaches such as ATDD – Acceptance Test Driven Development – and BDD – Behavior Driven Development. In this way, these models can be shared between the product owner, the testers and the developers (the three amigos) to define accurate acceptance scenarios, and to help clarify the business needs, as well as producing the test documentation, and the executable test scripts. We will also show how MBT techniques and tools has evolved the last period (what we call MBT 3.0) in order to provide a short learning curve and good usability by functional testers, the adaptation of MBT to iterative and incremental development lifecycle, and also the supporting both manual and automated test execution and a seamless adaptation from the first one to the second one.
Navn: Bruno Legeard, Virksomhed: CFTL
Presentation is in English.
Tilbage til toppen.