Functional Test
Many Development teams consider unit tests manual/ automated (e.g. Junit tests) as the Definition of Development is Done (DDD). I have observed this mind set in both product engineering teams and service delivery focussed teams.
In start up engineering mode, this is the norm. Everything testing takes a backseat for execution speed which is the right approach when the team is looking to validate a MVP and winning the much required buy-ins for getting into the investment stages.
I would not blame this mindset on the make up of these engineering teams. The Functional Test mindset needs to come from top down. It needs to be coached into the team by the leadership. Functional Test mentality should be part of each step of the development lifecycle. Its different but not hard to do and has some distinct advantages.
What is Functional Test?
Found a wikipedia definition:
black-box testing that bases its test cases on the specifications of the software component under test
What's it to a paying Customer?
As a paying customer of a service delivery or a sponsor/ product owner of a product development effort, Functional Test development is certainly the type of effort for which I would be happy to pay.
Yes, spend towards Functional Test Development effort is additional. But this spend on Functional Test automation gives the sponsor a benchmarked method of receiving software/ engineering results that prove that the specifications have been met.
Savings is not just One Time
Functional Test methods reduce release on release spend in accepting software (both manpower savings and quality). Team changes or service provider changes do not impact transition of functional knowledge since if its there in the tests, its straightforward for a new team member or a new team to pick it up.
The toolsets and kits available for Functional Test automation is exhaustive, there is little need to setup additional teams/ team members for Functional Tests. The development team members must be coached to setup and maintain tests that prove acceptance to stakeholders.
DevOps improvements have ensured that there is enough visibility at all levels regarding the quality of the engineering output.
Further Discussions on this subject
- The new Definition of Development is Done (DDD)
- Software Configuration Management and Continuous Integration Influences
- Functional Test emphasis in storyboarding
- Monoliths to Microservices - How Functional Test Architectures Change
- Functional Test Architecture - Black Box Fixtures, Test Runners, Dependency Service Mockers, Async Wait Handlers, System State Assertions and more
