Custom validation tests

[SAndreas]

Hi 

Is it possible to create custom module validation tests?

E.g. testing vi execution type to be matching with the default setting from template. (Prevent someone/scripts to change e.g. FGVs, start module... to reentrant)

[joerg.hampel]

Hi Andreas,

thank you for your trust in DQMH and for reaching out.

We've been talking about a kind of plugin structure for the DQMH validator to facilitate just this (adding proprietary tests), but it is nothing that exists as of today. However, please head over to the DQMH Feature Requests and post your idea there!

As for the specific example you mention, (some of?) the reentrancy settings are already checked by the validation tools:

• Non-Reentrant Event VIs
• Non-Reentrant Queue Class Overrides
• Non-Reentrant Reset Override
• Non-Reentrant VIs in Cloneable Module Library
• Reentrant Cloneable Start Module

If you feel that we have missed some things in regard to reentrancy, again, please feel free to suggest them over at the DQMH Feature Requests.

Cheers,

Joerg

[SAndreas]

Hi Joerg

Thank you for the feedback.

I'll have to digging a little deeper into the behavior and will post the feature requests.

I have already detected that the three action engines

• Obtain Broadcast Events.vi
• Obtain Request Events.vi
• Clone Registration AE.vi

not reported or updated where if they are shared clones.

Steps to reproduce:

1. Create Project with a new clonable module
2. Change all non-reentrant VIs to shared clone
   
3. Run module validation and execute fix
   1. Start Module.vi will be updated and changed
4. Rerun module validation
   1. No issues reported