h3. Unit Test Strategy will be as follows:
<!--P { 	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px } -->{color:#000000}Snapshot of PS1 data on the night of October 19th.&nbsp;{color} {color:#000000}We will store these  extracts, and then must re-extract the data from the test environment{color} {color:#000000}{+}after{+}{color} {color:#000000}the support packs have been applied and{color} {color:#000000}{+}before{+}{color} {color:#000000}the unit  testing has occurred.&nbsp;{color}
&nbsp;{color:#000000}Please set aside at least 6 hours (preferably, a day) for  us to do that.{color}&nbsp;This is the first step in our testing.&nbsp; It  serves two purposes:&nbsp;1.&nbsp; Ensure that all extracts still run  successfully.2.&nbsp; We'll compare the files, byte by byte,  to find out if there are significant changes in SAP structures from which we are  extracting (new field lengths, for example), for which we need to adjust the DW  structures.&nbsp;The next step is running extracts after  unit or UI testing, or as these tests go on.&nbsp; We will do this at users' request  if they need to test something using the DW (we talked about this before, the  users need to request this in advance and that they need to specify exactly what  they want and how they are going to test it).&nbsp; We&nbsp;may also do it at our  discretion for more complex data areas.&nbsp;