Closed jshughes closed 8 months ago
Closing as done
This ticket is not work for the development team but guidelines on how I&T should. But this contains the requirement and how to test them.
@jordanpadams @jshughes Did you want us to test all the discipline LDDs or were there specific ones?
@miguelp1986 I think just pick a few. The more complicated the better.
I would say ldd-cart, ldd-geom, and ldd-img ? @jshughes any others you can think of?
The purpose of this test is to ensure that LDDTool successfully processes all the Disciplines LDDs. However, instead of testing toward the end of Integration and Test, the testing of LDDTool will be performed toward the beginning.
Background: Toward the end of each build cycle, all Discipline LDDs are processed and the results are posted to the PDS4 Website. However, if a bug is discovered, then there is typically little time to debug LDDTool.
Proposed Testing: 1) Identify the current set of Discipline LDDs 2) Run the prior released version of LDDTool and capture the .xsd, .sch, and ,xml files. 3) Run the to-be-released version of LDDTool and perform a DIFF against the output of step 2. 4) Identify any potential problems.
@jordanpadams @tloubrieu-jpl