Testing Without Using Up Monthly Limit

  • Profile Image
    Asked on September 21, 2011 at 01:18 PM

    Is there a way for me to test my forms without having my test submissions applied to my monthly limit?

  • Profile Image
    Answered on September 21, 2011 at 01:27 PM


    Unfortunately there is no way around this, once a user submits data
    using the form it is automatically saved as submission and is
    counted on your quota.

    Thanks for using JotForm.


  • Profile Image
    Answered on September 21, 2011 at 01:30 PM

    Thank you for your reply. I'd like to suggest that this be modified so developers can test without those tests being applied to the quote.

  • Profile Image
    Answered on September 21, 2011 at 10:03 PM

    Hi Shawn

    You are certainly not the first to suggest this and will not likely be the last either. It may be a tall order for our developers but perhaps they can devise a way for the system to identify certain submissions as just tests and not have them be counted against allotted quotas.

    To explore this concept further, consider the possibility of having certain reserved strings for specific text fields that if used would trigger a "noCountAgainstQuota" function. Look at the following simple form:

    Let's say each of the entries above are reserved strings for those specific types of fields. If the form is submitted, with those exact entries, the submission should be recognised by the system as a test. (The only field that should not have any reserved strings would be Email because users would want to test to see if submissions are getting through, although we already have a button to test that in the email alerts:

    But getting back to the "reserved strings (Words)" idea, the "noCountAgainstQuota" function should only be triggered if all of the fields (except Email, for the reason already stated) contain only the reserved strings for the respective fields or nothing. Combo fields like Full Name and Address would be special: In the case of the Full Name, John must be entered in the First Name input and Doe in the Last Name. For instance, it cannot contain "John Brown" or "Jane Doe".

    That's the general idea but the whole concept requires far more thought and we would need to consider all of the ways that dishonest users (of whom there are few, I'm sure!) might try to circumvent it to their advantage,  like this guy :)


    ~ Wayne