[Analyses] If a saved verification pattern is badly typed, NuSMV throws an error
- open the attached model
- change the type of the port to int
- change the automaton accordingly: send an integer (any, does not matter) on the output instead of true
- open the "A/G, Contracts, Patterns"
- check the atom
Obtained behaviour: error "NuSMV terminated with ..."
Expected behaviour: AF3 error "this pattern is badly typed"