AMA: gaining confidence without integration tests

Lucy asks…

How do you gain confidence with the testing pyramid mentioned in this post? Unit testing is under the developers and you have only just enough e2e tests.

Continue reading “AMA: gaining confidence without integration tests”

AMA: the eye above my testing pyramid

Guido Cangelosi asks…

Why use an Illuminati semantic in “your” pyramid ? (and please, do not say “by chance”)

Automated Testing Pyramid

My response…

The eye symbol isn’t so much representative of the illuminati as I don’t consider testers or those who perform exploratory testing to be elitist or anything like that, it actually represents the eye of providence, which is an all-seeing eye.

I believe the role of a modern tester is more than just ‘testing’, it’s to advocate quality, that is make sure we have a good product, and that we have good automated tests (so we continue to have a good product).

So testers need to be an ‘all-seeing eye’ on both our product and our tests. It sits up there floating above the automated tests keeping an eye on them.

The diagram is missing some rays of light so perhaps I’ll include that on my next version :)

Introducing the software testing ice-cream cone (anti-pattern)

As previously explained, I like using the software testing pyramid as a visual way to represent where you should be focusing your testing effort, and often switch between using a cloud or an Eye of Providence to represent the manual session-based tests at the top of the pyramid that you should use to supplement and test your automated tests.

I often see organizations fall into the trap of creating ‘inverted’ pyramids of software testing, and only yesterday did a colleague point out to me that if you invert my pyramid with the cloud, you end up with an ice-cream cone! So, introducing the software testing ice-cream cone (anti-pattern)!