progression testing - on how regression test automation needs to be progressive to keep up with a...

12
Progression Testing Progression Testing Adam Knight Adam Knight Twitter: @adampknight Twitter: @adampknight Blog: www.a-sisyphean-task.com Blog: www.a-sisyphean-task.com https://www.flickr.com/photos/ https://www.flickr.com/photos/ openeye/5066018779 openeye/5066018779

Upload: adampknight

Post on 31-May-2015

434 views

Category:

Technology


3 download

DESCRIPTION

Discussing how regression test automation needs to consider the inevitable progression of software products over time, and therefore needs to be approached as an ongoing development process and not a produrement at the product inception.

TRANSCRIPT

Page 1: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

Progression TestingProgression Testing

Adam KnightAdam Knight

Twitter: @adampknightTwitter: @adampknight

Blog: www.a-sisyphean-task.comBlog: www.a-sisyphean-task.com

• htt

ps:

//w

ww

.flic

kr.c

om

/photo

s/openeye/

htt

ps:

//w

ww

.flic

kr.c

om

/photo

s/openeye/

50

66

01

87

79

50

66

01

87

79

Page 2: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

This is AdamThis is Adam

Page 3: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

This is AdamThis is Adam

Page 4: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

This is RainStorThis is RainStor

Service Manager n

NParchive

User Tools

Service Manager 3

Service Manager 2

Shared area

Stagingarea 1

ProductionDatabase 2

ProductionDatabase 1

Service Manager 1

Stagingarea 2

Working area(queue)

Information area(metadata)

Archive store(data)

Query Tool:npa_query

Query via ODBC:NParchive

ODBC Driver

ODBC-compliant

3rd Party Tools

Admin tool:npa_admin

Import Tool:npa_import

Export Tool:npa_export

Import Engine

Admin Engine

Query Engine

Query via ADO:NParchive

ODBC Driver

ADO-compliant

3rd Party Tools

Page 5: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

This is RainStorThis is RainStor

Page 6: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

Lack of Progression is RegressionLack of Progression is Regression

• Bugs can arise where functionality has not Bugs can arise where functionality has not changedchanged

• Customer expectation has changedCustomer expectation has changed• The market has moved onThe market has moved on• We can move backwards by standing stillWe can move backwards by standing still

•im

ag

e :

ray w

ew

erk

a

htt

p:/

/ww

w.fl

ickr

.com

/ph

oto

s/pic

fix/4

40

92

57

66

8

Page 7: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

Automation is software development Automation is software development

• Focus on needs rather than toolsFocus on needs rather than tools• Iteratively improve to introduce test Iteratively improve to introduce test

capabilitiescapabilities• Incorporate newly added product features Incorporate newly added product features • Adapt to new environments and Adapt to new environments and

technologiestechnologies

• htt

ps:

//w

ww

.flic

kr.c

om

/ph

oto

s/fr

an

cois

maill

ot/

htt

ps:

//w

ww

.flic

kr.c

om

/photo

s/fr

anco

ism

aill

ot/

83

33

42

29

64

/8

33

34

22

96

4/

Page 8: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

This is a RainStor Test PatternThis is a RainStor Test Pattern

Page 9: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

This is a RainStor Test PatternThis is a RainStor Test Pattern

Page 10: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

Test Harness Requirements ChangeTest Harness Requirements ChangeFrom Through To

Data Import and Query

Administration Commands

Full Cluster Administration

Single Server Single Process

Multi-server single pack

Multi-server parallel Packs

Sequential Packs Iterative Execution Parallel Iterative Execution

No ODBC/JDBC ODBC/JDBC single thread

ODBC/JDBC multi-thread

Text Based Reporting

Simple HTML Report

Interactive HTML with Summary and Differences

Linux Only Linux, Solaris, AIX, HPUX and (gasp) Windows

Linux Only

Page 11: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

ThanksThanks

• Email: Email: [email protected]• Twitter: @adampknightTwitter: @adampknight• Blog: Blog: http://www.a-sisyphean-task.com

• Email: Email: [email protected]• WebSite: WebSite: http://www.rainstor.com

Page 12: Progression testing - on how regression test automation needs to be progressive to keep up with a changing product

ReferencesReferences• Further ReadingFurther Reading• From smart peopleFrom smart people• http://lizkeogh.com/2011/03/04/step-away-from-th

e-tools/

• http://testobsessed.com/2011/02/the-atdd-arch/• From meFrom me• http://www.a-sisyphean-task.com/2011/03/without-http://www.a-sisyphean-task.com/2011/03/without-

stabilisers-why-writing-your.htmlstabilisers-why-writing-your.html• http://www.a-sisyphean-task.com/2012/10/moving-http://www.a-sisyphean-task.com/2012/10/moving-

backwards-by-standing-still-how.htmlbackwards-by-standing-still-how.html