since we can autogenerate asserts, we should provide a helper architecture to provide combinatorial input to test methods, join their result and assert against that.
e.g. a method taking two bools as arguments, should get 4 inputs, each of which must be applied
but also composite types must be creatable in the same manner, with plugability such that the end user can specify how to create bespoke types. Eg a class Person with a first name, surname, zip code and address
maybe provide a testresultclass, that is more or less an array of strings which are stateprinted actual results.
since we can autogenerate asserts, we should provide a helper architecture to provide combinatorial input to test methods, join their result and assert against that.
e.g. a method taking two bools as arguments, should get 4 inputs, each of which must be applied
but also composite types must be creatable in the same manner, with plugability such that the end user can specify how to create bespoke types. Eg a class Person with a first name, surname, zip code and address
maybe provide a testresultclass, that is more or less an array of strings which are stateprinted actual results.