According to section 4.4.1 of ISO 11607, “all test methods used to show compliance with this part of ISO 11607 shall be validated and documented.” AAMI Technical Information Report (TIR) 07, reiterates the point in 5.2.1: “All test methods must be validated.” ISO 11607 and TIR 22 then point users to Annex B’s list of “suitable test methods.”So are the methods of Annex B all you need?“If you follow ISO 11607, an FDA consensus document, and use the test methods in the annex, you don’t have to create your own rationale as to why another test is appropriate,” explains Jackie Daly Johnson, president of Beacon Converters (Saddle Brook, NJ) and cochair of the AAMI Sterilization Packaging Working Group, which developed TIR 22.PDK can run your unit tests on a module’s Puppet code to verify that it compiles on all supported operating systems, and that the resources declared will be included in the catalog.PDK cannot test changes to the managed system or services.“You don’t have to reinvent the wheel every time.”Many of the methods listed in the annex have been recognized by FDA as consensus standards.
By default, this command runs metadata validation first, then Puppet validation, then Ruby validation.
You can send module validation output to a file in either JUnit or text format.
You can specify multiple output formats and targets in the same command, as long as the targets are each unique.
Optionally, PDK can autocorrect some common code style problems.
You can customize it to validate specific directories or files in the module, or validate only certain types of validation, such as metadata or Puppet code.
Search for validating test:
As an alternative you can also try our non-DTD-based validator.