make method implementation check optional

[SierraGolf]

problem
currently all tests check that the method to be tested is implemented. this may be inconvenient if the class under test is an extension of another class and reuses the super classes method with overriding it. in case that the super class is an abstract class it may not be possible to test this implementation with the current architecture of the beast.

question
should the method implementation test be turned on or off by default? what is the more common use case?

solution
add a configuration to the abstract test builder to allow the user to enabled/disable the method implementation check.