I suggest creating a list of critical nav components, then make sure there are tests that run quickly marked with the “smoke” category that uses each of those components.
• Error Models
• Tracking Files Set
• Accept Filter
• Reject Filter
The number of scripts is not as important as having a set of scripts that flexes all nav. components… So if a script does batch estimation with an error model and an accept filter, it checks off three of the features.. These are not meant to test rigorous numerical results, in fact, running fast is really important because developers run these just about every day..