Hi, Thank you for your answer. For me Unit test is "testing bits of your code in isolation with test code" DI jobs will create a sas file with different behaviors so how do you test "each" behavior with one unit test. The greatest pitfall is that developers test too large a unit, or they consider a method a unit. This is particularly true if you don't understand Inversion of Control - in which case your unit tests will always turn into end-to-end integration testing. Unit test should test individual behaviors - and most methods have many behaviors. Any clue howto do that?
... View more