Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 442
  • Last Modified:

Efficient Procedures or Guidelines for Testing SAS data?

I am looking for a best, quick, and efficient way to test SAS data (output files, records, counts).  I am talking about the process, which is done after all SAS software programs have been written, and everything is already works, as it should.
Everyone test SAS data in their different ways, but I am looking the way that is more efficient and fast as well.

Currently, my SAS data testing includes the following bullets. Please shortly describe what you are doing for these bullets (short sub bullets will work as well).

1. Review Documents
2. Identify Requirements
3. Develop Test Data
4. Values to include in the testing data
5. Simulate command procedure and/ or parent module for testing
6. Test the Program


Note: Please do not refer me to links with testing guidelines, - I probably already read them. I am looking for the way that works for you.
Any comments or suggestions would be very appreciated!
Thank you in advance!
0
labradorchik
Asked:
labradorchik
  • 2
1 Solution
 
Aloysius LowCommented:
there isn't really an efficient way if you are talking about developing from scratch, especially ETL rules and logic... at least not for me

the most efficient (actually i would call it convenient) way i had was to take an existing set of data produced by the existing process, and do a PROC COMPARE, row by row, value for value to ensure that my process produces the exact output as the existing one...

otherwise, it's the slow way of producing expected results based on the input data for a sample set of records, bearing in mind to include records which has borderline values or special values and exceptional cases which the ETL is expected to handle..
0
 
labradorchikAuthor Commented:
lowaloysius, thank you very much for your comments!
I am sorry, I guess I meant to say "Independent Testing" way, -when there is no existing output data or you would even have to create your own input data (much smaller in size) for testing purposes.

Am I missing anything from these main bullets below while my independent testing?  Or any of these bullets can be eliminated or may be there is an another step that is missed?

1. Review Documents
2. Identify Requirements
3. Develop Test Data
4. Values to include in the testing data
5. Simulate command procedure and/ or parent module for testing
6. Test the Program
0
 
labradorchikAuthor Commented:
Thank you, lowaloysius! I already put together my testing plan.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now