Tests your pipeline might be missing

© COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 1

@CoverosGene

Tests Your Pipeline Might Be Missing

Build confidence that you have a

viable candidate for production

It’s about process, n

ot tools


@CoverosGene

Everything can’t be first or last

Do just enough of each type of

testing early in the pipeline

to determine if further testing is

justified.


@CoverosGene

Check your code footprint

mvn dependency:treemvn dependency:analyze

mvn com.ning.maven.plugins:maven-dependency-versions-check-

plugin


@CoverosGene

Poor quality code is harder to maintain

… and harder to secure


@CoverosGene

Are your libraries up-to-date?


@CoverosGene

Test your unit tests

Mutation testing


@CoverosGene

Test what users can’t do… or at least shouldn’t

User role testing


@CoverosGene

Security testby piggy-backing on functional tests

OWASP ZAP

passive proxyactive scanner

fuzzer


@CoverosGene

Repeatable, reliable deployments… and test that through practice


@CoverosGene

Audit yourself


@CoverosGene

Is the base system secure?


@CoverosGene

Are your packages up-to-date?


@CoverosGene

How’s performance?


@CoverosGene

Test the database


@CoverosGene

What are your users doing?


@CoverosGene

Practice failure


@CoverosGene

Scan all the systems

Don’t forget the infrastructure


@CoverosGene

Protect against hackers … even on dev and test systems


@CoverosGene

Don’t expect that your pipeline is done

A little better is still better.

Keep improving.


@CoverosGene

Test your pipeline… if it goes down, everything goes

down

Tests your pipeline might be missing

Software