1. What
   1. While a unit test focuses on small-scale design, a subcutaneous test does not address design, but instead tests basic inputs and outputs of the system as a whole
      1. https://lostechies.com/jimmybogard/2010/08/25/an-effective-testing-strategy/
   2. run with the same test framework as the unit test
2. Why
   1. to avoid difficulties with hard-to-test presentation technologies
      1. faster than testing through the UI
      2. https://martinfowler.com/bliki/SubcutaneousTest.html
   2. to speed up the information pipeline about an application
   3. to reduce the reliance on UI driven tests for checking functionality
   4. to create better end-to-end tests
      1. using the existing code, framework, and/or libraries
   5. to reduce test flakiness and focus on functionality
   6. No browser, no screenshots
3. Sources
   1. https://www.ministryoftesting.com/dojo/lessons/introduction-to-subcutaneous-testing
   2. https://appdevelopermagazine.com/focus-on-subcutaneous-test/
   3. https://github.com/giamir/subcutaneous-testing
   4. https://github.com/robdmoore/SubcutaneousTestsPresentation
   5. https://robdmoore.id.au/blog/2015/01/26/testing-i-dont-even
   6. http://josephwoodward.co.uk/2019/03/subcutaneous-testing-asp-net-core