Problem:
When creating a Job and checking how it looks (including reviewing custom emails, etc.):
The visits to the resulting page are counted in the analytics
Any test application will also be counted in the analytics
This situation can skew the analytics of a given Job.
Request:
Allow to have methods to test a given Job without adding to its analytics.
For instance:
Allow for some given (custom/random?) code to be passed in the QueryString that would not trigger the visit count
Allow for some test email (maybe those of the Team?) to be defined so that it can be used without triggering counts
