Generating the pack file from source code– The same trusted application code can be used for several generations or even different platforms, but the way that we generate the final trusted application package might change. This is why checking which tools (and which versions) were used for generating the trusted application is important to ensure that the final production trusted application will be aligned for the relevant project. One of the most important aspects here is the used .jar file (e.g. isdi.jar) that defines the APIs exposed by the firmware, which is different across generations and platforms.
Pre/Post-signing validation- As mentioned before, most of the validation will be done on the pre-production version of your trusted application. But in later stages, you are expected to cover the same flows with the production version as well.
DALP package validation- Additional step of the validation is creating and validating the content of the DALP package which contains various versions of the trusted application, each matching a different platform type or generation of platform. There are various limitations on what should go to into the DALP package, so the validation team should ensure that the correct pack files with valid values are packaged into the given DALP. Having invalid values, e.g., for the platform type or versions, might lead to installation failure on different setups. This is why testing the same DALP on various platform types and generations is mandatory.