4 ms·

i use the combination of assert-driven development + UI/UX testing. (manual, but that could be a valid candidate for automation in my projects) so I'm not say

i use the combination of assert-driven development + UI/UX testing. (manual, but that could be a valid candidate for automation in my projects) so I'm not saying there are no scenarios, but they all end up being the customer facing scenarios, and verifying those meet expectations. Also just developers making sure the functionality "works" naturally catches the technical bugs (because asserts in production code would cause the app to crash)

eru 13y ago
You might be interested in `contracts' which are basically assertions on steroids. See https://en.wikipedia.org/wiki/Design_by_contract https://en.wikipedia.org/wiki/Design_by_contract (or http://blog.racket-lang.org/2012/11/contracts-for-object-oriented_4671.html http://blog.racket-lang.org/2012/11/contracts-for-object-ori...) for an introduction. You might also want to explore QuickCheck, which helps to generate these scenarios.