All of the SDR teams used these data sets to define instrument configuration parameters (or calibration LUTs), SDR algorithm refinements, related instrument upgrades, and instrument waiver mitigations. For example, the VIIRS test data sets enabled the development and verification of Day-Night-Band (DNB) geolocation code changes needed to account for the differences in aggregation modes. The test data also allowed detection and prompt fixes of IDPS code defects that prevented correct data processing (e.g. scan encoder values, cold FPA temperature). The OMPS test data sets were extremely useful for the development of new J-1 Application Process Identifiers (APIDs), the new feature of compressing the counts, and a new flight software version. The OMPS43A test data were particularly helpful since these data sets have realistic counts with the real earth view spectral signatures and realistic geo-location. The OMPS43B data sets were useful for testing both the SDR throughput and the decompression algorithm. In addition, proxy S-NPP 17-Day ROOD data sets allowed functional verification of end-to-end data flow to ensure J1 readiness of Cal/Val monitoring tools such as the Integrated Calibration and Validation System (ICVS). Availability of these test data sets have helped to avoid delays from pre-launch testing and algorithm delivery to the ground processing system readiness. Despite meticulous care from the TDWG in making these test data sets, and despite achieving good pre-launch characterization of the JPSS-1 instruments using these data sets, the science teams still realized some limitations and possible improvements of these data sets to adequately address all of the algorithm upgrades as expected from post-launch on-orbit data. As a result, the JSTAR science teams felt the need for improved coordination between the science teams, flight teams, and the instrument vendors during TVAC measurement phases and test procedures. This paper discusses the lessons learned through these test data sets and steps needed to define and improve the utility of pre-launch test data sets for the future JPSS-2 pre-launch characterization and testing.