software architecture...yes, on tests!

Software architecture...Yes, on tests!Annarita De Biase – SDET II Miro Barsocchi - SDET IICamillo Quatrini - QA Evangelist

ROME 18-19 MARCH 2016

Hotels.com

Introduction

Introduction

Introduction

Waterfall - Agile

A bit of history…

Long T.T.M.

Ping Pong Effect

Quality Delegation

Enemy Necessary

A bit of history…

A-TEAM Share Quality

A bit of history…

Things that did NOT work

Things that did NOT work

Things that did NOT work

Things that did NOT work

Monolite

Oracle

Complex

Misunderstood

Things that did NOT work

All In One

Unmaintainable

Overflowing

Front end

Modularization

Competency division

Library usage

Decoupling data/tests

Good working – Front end

Back end

Framework Java Code

Env Configurations

Java for Tests

Test Inputs

Test Outputs

Good working – Back end

Java code centralizedJava code general

Code extensible

Maintainable

Readable

Steps to reach the freedom

INTERFACE

CORE

Core Functionalities

Common Interface

Input Format

Output Format

Extensions (if needed)

Practical Applications

TEST MODULEJAR JSON

CORE(JAR)

REPORTCREATIONB

AC

K-E

ND

FRO

NT-

EN

D

Srcdata

NIGHTWATCH

REPORTCREATION

INTERFACEJAVASCRIPT

EXT#1

EXT#2

EXT#n

EXT#1

EXT#2

EXT#n

Conclusion

@CamilloOdkcquatrini@expedia.com

https://it.linkedin.com/in/camillo-quatrini-1934558a

Thanks!

ROME 18-19 MARCH 2016

All pictures belongto their respective authors

@MiroBarsambarsocchi@expedia.comhttps://it.linkedin.com/in/mirobarsocchi

@AnnaritaXadebiase@expedia.com

https://it.linkedin.com/in/annaritadebiase84

Roma-Agile-Testing-Meetup