Modern Software Testing

As a follow on from my last post about Martin Fowlers article on Testing Shapes e.g. Pyramid and Trophy), Tim Bray‘s post on modern software testing (or, “Testing in the Twenties” as he titled it) caught my eye. Bray believes that these Testing Shapes are “misshapen blobs” that are all “seriously wrong in important ways”. I do like people with opinions 🙂

(more…)

Tags: integrationtesting, testshapes, timbray, unittesting

Blog post summary: Test Shapes by Martin Fowler

In his post, “On the Diverse And Fantastical Shapes of Testing“, Martin Fowler talks about the Test Pyramid and Test Trophy, but concludes that the proportions suggested by each are much less important that writing fast, reliable, expressive tests with clear boundaries.

(more…)

Tags: integrationtesting, kentbeck, martinfowler, testdoubles, testpyramid, testshapes, testtrophy, unittesting

Testing in Production Presentation – SVCC 2018

The following post is essentially a written version of the Testing in production talk I gave at Silicon Valley Code Camp 2018. You can find the presentation deck here at slideshare.

(more…)

Tags: chaos, chaosengineering, conferencetalks, For prep, integrationtesting, itestinprod, mytalks, production, resilience, resilienceengineering, Testing, testinginproduction

Testing in Production

Note that I gave a talk on this blog post in Dec ’18, if you prefer to watch that: https://www.youtube.com/watch?v=-b4QaEuFkP0

 

“Testing in production” used to be a joke. The implication was that by claiming to test in production, you didn’t really test anywhere, and instead just winged it: deploying to production and hoping that it all worked. Times have changed however, and testing in production is becoming accepted as a best practice.

(more…)

Tags: integrationtesting, itestinprod, production, talks, Testing, testinginproduction

Running an individual unit test with maven

Individual tests can be run from maven. This must be done from within the folder that contains the source (as in the folder that contains src/test/java), which will likely be either be the root of your maven project, or in one of your modules.

For surefire (unit tests), to run a whole test class, this will be something like:

mvn -Dtest=com.your.package.YourTest test

or, to run a specific test method:

mvn -Dtest=com.your.package.YourTest#testMethod test

For failsafe (integration tests), it will be something like:

mvn -Dit.test=com.your.package.YourIT verify

This is covered in the maven surefire plugin docs and maven failesafe plugin docs respectively, but those examples don’t mention packages names, which are required.

Tags: failsafe, integrationtesting, JUnit, Maven, mvn, surefire, Testing, unittesting