Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Preview:

Citation preview

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

Moving from Ad Hoc Testing to Continuous Test Data with

FitNesse

Agile Testing Days

Joris Meerts, 12 November 2014

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

about me

• Joris Meerts

• Software tester since 2007

• Capgemini

• www.testingreferences.com

• Context-driven school

• Member of the Dutch Exploratory Workshop on Testing (DEWT)

• @testingref

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• The context

• The starting point

• FitNesse

• Java

• Some lessons learned

outline

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

The context

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• Legacy e-commerce database

• Many (190+) complex tables

• Many stored procedures, triggers

• Complex scheduling

• Hardly any functional documentation

• Processing may take days or weeks

the context: the system

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• Agile team

• 1 - 2 senior testers

• 4 - 6 senior database developers

• 1 product owner

• 1 scrum master

the context: the team

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

The starting point

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

Why automate?

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• Ad hoc testing

• No scheduled tests

• ‘Technical tests’ in FitNesse

• No use of development tools for test code

the starting point

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• FitNesse, Java, JUnit, Jenkins, Eclipse

• Advanced SQL, PL/SQL

a first time for everything

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

FitNesse

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

test architecture

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

why I would recommend FitNesse

• All purpose tool

• Modularization

• Separating data from tests

• Symbolic links

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

all purpose tool

• Database

• REST interface

• SSH / Telnet

• FTP

• No GUI automation

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• Use of building blocks

• Parameterized includes

modularization

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• Include test data in the scripts

• Restrict the use of test data

• Easy to find out where the data is used

• Use scripts to check configuration

separate data from tests

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• Symbolic links

• Templates

• Tags

other useful things in FitNesse

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

Java

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

or…

how to learn programming in a

nutshell

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• JUnit for testing

• Very easy build and deploy

• Eclipse for development

• OpenJPA replacing scattered SQL statements

some wonderful things about Java

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

Some lessons learned

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

some lessons learned

• It is not easy to strike a balance between developing test automation and (exploratory) testing.

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

some lessons learned

• Code that is hard to test can really drainthe energy out of the test automation effort.

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

some lessons learned

• Test automation does not become a team effort by placing it in the definition of done.

• Who should write the test code?

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

Determination is an important success factor.

some lessons learned

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• Data is running through the system.

• We are able to observe system behavior.

• We are able to test some features better.

• Test automation catches bugs.

conclusion

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

• Gojko Adzic - Test Driven .NET Development with FitNesse (2009)

• Stack Overflow

• Bruce Eckel - Thinking in Java (2006)

some useful resources

Moving from Ad Hoc Testing to Continuous Test Data with FitNesse

Joris Meerts, 12 November 2014

joris.meerts@capgemini.com

@testingref

www.testingreferences.com

patternsofproof.wordpress.com

thank you for attending my presentation

Recommended