Præsentationer 2016

 

---

Her kan du læse mere om indlæggene på konferencen

Application Security Testing – A New Approach

Two years ago I was filled with hope that all Testers would acquire the necessary skills to become security-aware. Some certainly did, but most did not. What went wrong? Security is a difficult subject to learn and I now appreciate it was not realistic to expect many people to become confident security testers.
I hunted for a better approach to accommodate minimal tester engagement yet provide genuine security for organizations that are open to trying new ideas. The quest took me through a much deeper understanding of security testing tools and how they really worked. Considering why so many techniques didn’t really benefit security led me to a new concept that turns our usual intrusive model of testing inside-out.
The very new answer is real-time Interactive Application Security Testing (IAST). This technology employs sensors to report security attributes out of the applications using API instrumentation, without submitting any security test cases. I will explain how IAST eliminates the security bottleneck that often slows down delivery or de-scopes important tests. This new sensor-based approach doesn’t require expertise in security and is about to revolutionize testing, especially for Agile and DevOps. You could be the Danish experts in real-time security within weeks!

Tilbage til toppen.

 

Styregruppens anvendelse af testresultater til styring af leverancer

I forbindelse med større it-leverancer giver testresultater en god indikation af fremdrift, kvalitet og risici i projektet. Hvordan sikre du, at din forretningsledelse i styregruppen har denne indsigt og hvordan forbereder du dette punkt.
Tilbage til toppen.

 

Kend din kvalitet – og prisen for den

Dette indlæg omhandler praktiske erfaringer med hvordan man sikrer at ens software er tilstrækkelig god inden release. Hvilken indsats der skal til for at sikre kvaliteten og hvilken omkostning det medfører. Forskellige eksempler omkring planlægning og styring af udviklings- og test indsatsen bliver gennemgået herunder learning points omkring brug af manuel og automatiseret test.
Tilbage til toppen.

 

Klar og tydelig kommunikation, tak

En af de væsentlige opgaver som topleder er at have fokus på, at løsningerne bliver leveret til tiden i den aftalte kvalitet. Derfor er det vigtigt at have redskaber til dette gennem hele projektforløbet.

Et af redskaberne er den løbende kommunikation fra programmets eller projektets testmanager, om hvad kvaliteten af projektets leverancer er gennem hele projektets levetid. Det er derfor vigtigt at testmanageren kommunikerer klart og tydeligt i et sprog som topledelsen kan forstå, så der løbende kan træffes de rigtige beslutninger på et oplyst grundlag.

Tilbage til toppen.

 

Quality for the Digital Enterprise – Mobile QA and Testing Strategies (workshop)

There are more than 12 billion connected devices in the world—more smart “things” than people. Innovative companies are adopting Internet of Things (IoT) strategy and technology to rethink their products and services and redefine their relationships with customers, employees and partners.
Connecting the sensors, devices and machines in the physical world to the Internet creates multiple new digital opportunities for industries. Organizations are increasingly focused on creating an engaging and consistent digital experience across every touch point, and at the heart of the digital experience is ‘mobility’.
Implicit in all of this, the digital enterprise demands a new breed of quality assurance and testing, that is more outcome focused and not input-driven.
In this workshop you will learn more about the testing challenges in the new digital and mobile age and discuss concrete solutions for manual and automated testing of mobile devices and apps. You are invited for an interactive workshop to discuss mobile testing issues and share experiences. The workshop will also include as a demo of cloud-based solution for mobile app testing, comparison of different tool options and presentation of different techniques.

Discussion points:

Internet of Things (IoT)

The challenges in Mobile Testing and QA

Device selection and Infrastructure

Testing Processes and Approaches

Tool Selection and Automation

Customer Experience Testing (CxT)

 
Tilbage til toppen.

 

Kend din leder (workshop)

Ved du, hvordan en topchef forholder sig til test?
På denne workshop har du mulighed for at vurdere, om du er i øjenhøjde med din leder. Hvis ikke kan du diskutere med de andre deltagere, hvordan du kommer det.

Tilbage til toppen.

 

Testers needed on agile teams!

On smooth-running agile projects, developers usually write plenty of unit tests. So what is there for testers to do? Actually there are plenty of important problems to solve: 1) How do we help ensure that those unit tests are of high quality with good coverage? 2) How do we best divide the automated tests into unit tests or end-to-end tests? 3) Based on our knowledge about the automated test coverage, how do we plan and efficiently perform explorative manual testing? In this talk I will discuss these questions based on examples and experiences from Danish and American software projects.

Tilbage til toppen.

 

BDD i en verden af agile – set fra en testers synspunkt

Vi kender det alle, en vandfaldsopgave solgt som værende agil. Tilføj BDD som ekstra krydderi. Dette rejser uværgeligt spørgsmålene: Hvori består testopgaven? Hvad er testerens rolle? Hvilke testprodukter er output fra denne dødsspiral? Disse spørgsmål er omdrejningspunktet for indlægget.
Tilbage til toppen.

 

The beginning of a SAFe journey at LEGO

About a year ago, management in the digital agency at The LEGO Group decided to scale their agile activities using the Scaled Agile Framework aka SAFe. Learn more about SAFe, how our journey began, where it took us, and what we have learned so far – including observations with a perspective on quality. I aim at providing you with some key takeaways to consider for using the framework in your own organisation.

 

Hvorfor et agilt mindset er vigtigt for IT udviklingsprojekter?

Dynamik, kompleksitet og usikkerhed præger i stigende grad organisationer og deres omverden. Det har store konsekvenser for gennemførelsen af IT udviklingsprojekter, og forståelse for kompleksitet og håndtering af komplekse problemstillinger, er livsvigtig i jagten på succes med IT udviklingsprojekter.
Her spiller det agile koncept en fortsat større rolle i projekt, udviklings og test-disciplinerne, men hvorfor er det? Og er agilitet en fordel i alle sammenhænge? Hvad vil det kræve af min organisation eller af mit projekt, at få succes i komplekse situationer?
Kom og få indblik i kompleksitetens verden og hvorfor et agilt mindset i projekt, udviklings og testdisciplinerne kan bistå IT udviklingsprojekter i komplekse situationer.

Tilbage til toppen.

 

Test Planning in Agile Projects

In this presentation we will take a dive into test planning in projects based on a SCRUM-setup, in order to investigate which parts of the test plan is important in different contexts, how we find out what the context is and of course, also see if we really need a test plan at all.
Many test managers create test plans based on “the one we used in the last project”. In some cases that test plan can be traced back to a time well before projects were run in an agile fashion, and these monsters from the past can in themselves present a risk: they are too big and too difficult to work from, when you’re inside a 2-week sprint. Essentially this leaves us with the choice of having a test plan on the side of the project, to just get the checkmark, so to speak, or seriously rewamp the test planning into the SCRUM setup, discarding the bits which are no longer useful and adding as well as clarifying how we want testing to be, now that we are doing SCRUM.
The questions we will seek an answer to are:

why do we even do planning of testing?

who is the test plan for?

what should be in it and why?

when do we plan testing in SCRUM and when do we stop planning?

who should do the planning?

 

I hope that the audience will take the answers to these questions with them back to their own projects, and give them insight into a few tricks to enable them to plan quickly and efficiently for their future testing work.

Tilbage til toppen.

 

Øg sporbarhed og produktivitet gennem integration

Krav, epics og user stories er ofte elementer, som bliver brugt I mange discipliner og derfor også ofte flere værktøjer gennnem udviklingsprocessen.

Det er vigtigt at sikre man har de rigtige krav, men også at disse krav er up-to-date og er der, hvor man skal arbejde videre med dem.

Krav bliver oprettet af forretningsanalytikere i et værktøj, udviklerne sørger for at omdanne disse til epics og brudt ned til user stories I et agile planlægningsværktøj, mens testerne styrer testplaner og test cases I et helt tredje værktøj.

Så er det altså lidt svært at finde ud af, om et krav er dækket af en test, hvilken kode man skal kigge på, hvis den fejler og om det påvirker andre krav.

Det er dog ikke kun kravene, der kan være problemer med. Testere og udviklere skal arbejde sammen om at finde og løse defects, men mens test teams benytter test- og defect management værktøjer, så foretrækker udviklerne at håndtere

deres opgaver I issue trackers eller agile planlægningsværktøjer.

Dette manglende samspil skaber et split mellem de teams, som det er meget vigtig  er alignet for at sikre en effektiv udviklingsproces.

Generelt set er det svært at få det man populært sagt kalder “one version of the truth”, når man arbejder på samme elementer I forskellige teams og værkøjer. Ved hjælp af integration kan man sikre, at man ikke kun kan rapportere på værktøjets egne informationer, men kan berige rapporter med data fra andre systemer.

Gennem dette indlæg vil Testhuset fortælle, hvordan de sammen med deres kunder har sikret det rette samspil og effektivisering af udviklingsprocessen og sporbarhed på tværs af værktøjer gennem integration.

Tilbage til toppen.

 

Nye teknologier, nye testmetoder – fokus på test af Cloud-baserede løsninger

De nye teknologiske trends kræver nytænkning af testen – SMAC-teknologierne, hvor Cloud er en af giver anledning til ny måde at tænke test på. Hvad skal testes, hvordan testes der, er der noget der ikke er muligt, hvad med risici, testernes profiler, forhold til interessenterne, lovgivningsforhold m.m. Alt sammen noget der bør tænkes ind i testen. I dette indlæg vil Ole komme ind på nogle af disse forhold, og give sit bud på, hvordan test af cloud bør finde sted. Ole har senest i 2015 været med til at opbygge et test framework for test af en cloud-baseret løsning.
Tilbage til toppen.

 

Testledelse på tværs af 140 organisationer

Case: Indførelse af en helt ny afregningsmodel for det danske energimarked

Folketinget vedtog i juni 2012 lov nr. 575 med det formål at fremme konkurrencen på det danske elmarked og gøre det mere overskueligt at være elkunde.

Denne case beskriver hele processen med at sikre at over 140 forskellige organisationer er klar til samlet idriftsættelse den 1. april 2016. Casen gennemgår alle de strategiske beslutninger omkring planlægning, involvering af interessenter og gennemførelse af testforløb for it-leverandører, netvirksomheder, elleverandør og andre interessenter.

Præsentationen vil gennemgå de praktiske tiltag, opbygninger af testmiljøer, selve eksekveringen, opfølgning og afslutningen af testforløbet.
Tilbage til toppen.

 

Elektronisk tinglysning – hvad gik galt?

I september 2009 gik den elektroniske tinglysning i drift som et big-bang. Teknisk set virkede systemet uden alvorlige problemer, men manglende brugervenlighed og organisatorisk implementering gav en national katastrofe der varede et halvt år. Medvirkende årsager var IT-arkitektens dogmatiske krav som leverandøren behændigt omgik, gode krav til usability der blev glemt undervejs, og en tvivlsom risikostyring. Kunne bedre test have hjulpet?

Tilbage til toppen.

 

Challenges in IoT Testing

In all currently commercially relevant big issues, such as Industry 4.0, the Internet of Things, smart mobility, smart grid, industrial data rooms, etc. the networking of technical components or software-based systems represents the central concept. The new approaches provide quality management with completely new requirements, since previously closed systems will be opened and connected to systems-of-systems (a guiding principle in the field of industrial 4.0). Proven secure end-to-end quality for functionality, interoperability, robustness, reliability and trustworthiness need to remain e.g. the hallmark of IoT solutions developed in Europe demanding increasingly reliability and security within the Internet of Things. For this new testing and acceptance methods are necessary, as this presentation will explain.

Tilbage til toppen.

 

Brug af model-baseret test af apparater

Carsten vil denne gang have den lidt nørdede tilgang, så temaerne, der bliver berørt er:

Hvad er en model?

Hvordan kan en model bruges til at generere test data?

Hvad er en pseudotilfældigtalsgenerator?

Tilstandsmaskiner, som model

Tiden som usikkerhedsfaktor

Tilbage til toppen.

 

Gevinsten ved at indtænke handicaptilgængelighed i programdesign

Hans Rasmussen og John Heilbrunn, der begge er blinde, vil give en præsentation af, hvordan man håndterer programmernes kommunikationsflader gennem brug af kompenserende programmel, der kommunikerer via syntetisk tale.

Programfladerne er normalt designet til brug med fuldt syn og dermed fuldt overblik, What You See Is What You Get.
Som bruger af synskompenserende udstyr samler man detaljerne op via tale og danner sig på den måde et mentalt overblik, der så bliver det handlerum, man betjener softwaren ud fra.

Vi vil illustrere problematikken generelt og gennem konkrete eksempler såvel på PC som på SmartPhone.

Tilbage til toppen.

 

Use Test Trees to get an Overview of the Test Work

Most testers have experience in the use of the classic test case design techniques to get inspiration for what we can test for a system or a part of a system, a so-called feature set or test-area. A feature set could be one or more user interfaces with underlying functionality or an internal component. But if the feature set is complicated and/or voluminous, then it can be difficult to get on overview of what you could test, and hence also difficult to decide what you are going to test to get an acceptable test coverage.

Based on actual user interfaces and rules this presentation will show how to construct a ‘Test Tree’ for a feature set.

A Test Tree could be compared to a simple version of a cause-effect graph or to a classification tree, where the coverage items for a the test conditions in a feature set are organized, so that you get an overview over, what can be tested for the feature set. Based on for example a risk analysis it is possible to choose the coverage items to test to achieve a coverage of for example 60 % coverage for the entire feature set, disregarding which techniques are used to derive the coverage items.

Test Trees can be used for any feature set no matter its size, and can, in addition to simple coverage also be used as the basis for more comprehensive testing, e.g. in the form of combinations of simple coverage elements.

Test Trees may also be used to express the expectations for a part of the system to be developed, for example to express precise and comprehensive acceptance criteria for user stories.

Come and get inspiration for using Test Trees for your testing; it will make your test more clear and visible.

Tilbage til toppen.

 

Testteknikker med inspiration fra hele verden

Klaus har arbejdet med test i 23 år og har delt sine erfaring om test på konferencer i 15 lande rundt om i verden, inklusiv Japan, Korea, Indien, Australien og USA. Klaus har taget inspiration med hjem fra disse konferencer, og i dette indlæg vil han præsentere nogle af de testteknikker han har mødt på sine rejser rundt i verden. Klaus vil også komme ind på de 11 mest anvendte testtekniker fra ISTQB Worldwide Software Testing Practices Report in 2015-2016.

Tilbage til toppen.

 

Optimize test planning across organization using domain specific catalogues

This presentation describes how a domain area in Danske Bank Group IT successfully raise quality across projects and maintenance teams by a targeted effort. The effort is driven by the departments “Advisory test manager”. Core elements of the effort are two highly facilitated test planning workshops which are based on domain specific catalogues. The workshops have been held for 1 ½ year and are very well received by both employees and management and have become a natural element in the development process. The form of workshops has proven to be easily conducted across different locations and across languages.

The presentation describes the workshops and the related catalogues and the organisation with department advisory test manager working together with project and team test managers.

Tilbage til toppen.

 

Cognitive Computing. Not science fiction, but a journey

In this session the potential of cognitive computing and how cognitive systems are implemented be briefly introduced, and the impact on system development and system delivery (including test) will be discussed. Systems based on Cognitive Computing are based on standard software which is fed with data, trained and provided feedback on its decision. IBM’s Watson is an example of a cognitive system.
How do we test a system which is constantly learning and thereby potentially changing the outcome of a certain operation? What are the new challenges that we need to tackle when developing and maintaining cognitive systems?
Peter will help us understand some of the challenges and give us some food for thought.

Tilbage til toppen.