A few months back I wrote an article that is the culmination of all my thoughts around software testing, I thought I should share it here :)
T shaped testing uses mostly black box component testing to test the plumbing and most use cases, complemented by unit tests for edge cases and core logic, and the traditional integration tests and end to end tests. This approach produces better refactor-ability / confidence / development speed / code coverage / ease for TDD, BDD / ease for outsourcing and remote working / ease for quick quality and completeness assessments.
Taking documentation to another level of quality is another major benefit.
The over-reliance of pyramid testing on traditional unit tests locks down the implementation details and spreads the solution for a requirement over many places, making it hard to refactor later or leverage the analysis of the original problem, besides being time consuming.
If you into .net core, this open source project contains examples and a nuget package to help you implement this.
This approach has been successfully tested in back end micro services and shared libraries, and it has the potential to help with desktop applications and front end; give it a try!
Further explanation can be found at https://www.linkedin.com/pulse/evolving-past-test-pyramid-shaped-testing-alan-sarli/
Top comments (0)