Test Engineering


Push … Build … Cross fingers

Test Automation is often rushed consideration, when the ideal is when it part of the build and deployment pipeline

Developers rightly do unit test, to test their code in an isolated way, but there are many layers to an application, and different issues can arise that can be be caught with UI or API tests.

With a maintained acceptance testing framework, you have effective environment to maintain effective automated testing, and prevent failing deployments (commonly down to basic issues).

I can bring effective test engineering to a project, with a “no waste” philosophy, which means a consistently useful testing framework.

More importantly it should grow in parallel with the application it is designed to test – the test framework then evolves naturally, as different test requirements surface.

Test engineering is not just about test automation; integration with development and devops is essential to maintain “testing momentum”, and encourage contribution from the team.

Test engineering is not just about acceptance tests either, important as they are to the project management flow. Non-functional requirements have acceptance criteria, just like any other user story.

Importantly it should be integral to the build pipeline, from development to production.  In tech, the value of a framework, is how far it permeates the project as a whole.  As a guide for developers and point of reference for the Product Owner.

Don’t underestimate the effort required to do good test engineering, and don’t underestimate how useful it can be.

testing-stack