topic Re: SAS Unit Test, DI Studio flow testing and managing data files on a SAS grid in SAS Programming

SAS Unit Test, DI Studio flow testing and managing data files on a SAS grid

Jason1 — Tue, 22 May 2018 10:28:24 GMT

Hi,

Would anyone know of any resources for the above? I have been asked to draft a list of testing guidelines / dev standards and was wondering if there is much info around.

Regards,

Jason

Re: SAS Unit Test, DI Studio flow testing and managing data files on a SAS grid

LinusH — Tue, 22 May 2018 14:26:34 GMT

Every implementation/system is kinda unique, but you wish for some eatable sizes for each part I guess.

SAS Unit test is for me equal SAS DI Job. And tested often by developer, and potentially fellow developer (four eye principle).

Job Flow might be tested by third person, like system admin (depending on your staffing).

Managing data (files) can be a whole library of best practices, and usually ave som many site specific constraints...so I leave it for now.

Re: SAS Unit Test, DI Studio flow testing and managing data files on a SAS grid

HeG — Wed, 26 Sep 2018 13:16:44 GMT

Hi,

We have DI jobs that we create.

In one DI job we have lots of tasks done.

How do you unit test your DI jobs?

If we write Macros, it is easy to have modules that we unit test. Different story with DI jobs.

//Henrik

Re: SAS Unit Test, DI Studio flow testing and managing data files on a SAS grid

Patrick — Fri, 28 Sep 2018 02:47:34 GMT

Unit testing is normally done by a developer (the primary developer or even better a peer). You execute the DIS job directly out of DIS or in batch and check against pre-defined unit test cases.

You check the log for any anomalies (warnings and the like; can be one of the unit test cases) and you check if you meet all the unit test cases - and you maintain a log of your testing with failure/success against each test case. Once complete/successful you handover your objects for the next level of testing.

Re: SAS Unit Test, DI Studio flow testing and managing data files on a SAS grid

HeG — Fri, 28 Sep 2018 06:18:15 GMT

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?