More on df_preview

Serge Tkachov

I would like to test some "live" forms to see if my custom fields actually save values to upload database.

I tried using df_preview with 4111111111111111 to create a valid test transaction and then examine data saved in custom fields - I don't see the transactions in my reports (custom reports in Data Management/Reports/Report Writer).

Can someone show me the way?

Thanks

-serge

Serge Tkachov

Dear Convio,

Our Convio site is live with some forms,

as we are creating more forms with different variations of custom fields, we would like see proof that the values we enter into these fields are actually saved to the database before we go live. Currently, the only way to do that is to submit a live transaction with valid CC number and dollar amount and then run a custom report to check the values. This testing becomes pretty expensive! (we can revoke the transactions, but this is not they way testing should be done)

Is there another way? df_preview or an invalid CCN does not save custom fields to database, or at least custom reports show them as empty.

Thanks,

-serge

Ken Cantu

Serge Tkachov:

Dear Convio,

Our Convio site is live with some forms,

as we are creating more forms with different variations of custom fields, we would like see proof that the values we enter into these fields are actually saved to the database before we go live. Currently, the only way to do that is to submit a live transaction with valid CC number and dollar amount and then run a custom report to check the values. This testing becomes pretty expensive! (we can revoke the transactions, but this is not they way testing should be done)

Is there another way? df_preview or an invalid CCN does not save custom fields to database, or at least custom reports show them as empty.

Thanks,

-serge

Hi Serge,

If Transaction Processing is live (it only wouldn't be during deployment) then you are correct in that the only way to test that information is captured and written to a constituent record is to test with a live card. Internally we use gift cards for this purpose and set the minimum value to be about 50 cents so we can test with low increments, you then have the option to refund those donations later to keep using the card.

If you are in deployment and Transaction Processing is not live then you can test as much as you want and it will write to the Constituent record because all that test data will get cleared out when we run through our Go Live checklist.

Unfortunately there is not another way test this for custom fields currently.

Thanks,

Ken

Serge Tkachov

Ken Cantu:

Hi Serge,

If Transaction Processing is live (it only wouldn't be during deployment) then you are correct in that the only way to test that information is captured and written to a constituent record is to test with a live card. Internally we use gift cards for this purpose and set the minimum value to be about 50 cents so we can test with low increments, you then have the option to refund those donations later to keep using the card.

If you are in deployment and Transaction Processing is not live then you can test as much as you want and it will write to the Constituent record because all that test data will get cleared out when we run through our Go Live checklist.

Unfortunately there is not another way test this for custom fields currently.

Thanks,

Ken

Hi Ken,

Thanks for the quick reply.

There is a general problem in the Convio form development that it doesn't have a testing and staging environment.

We can develop and test how the form looks and works until the point of submitting data, but I can also test that locally on my computer too.

The two areas that I would like to see improvement on is submitting and viewing "all" entry field data so that we can confirm that data was submitted and it was submitted in correct format and second, test the generation of email responses upon submission. As a university, we have stringent rules on how the email is formatted and it needs to look formal. We also use data from the form and/or from the database on the response emails.

These improvements would help greatly in our development, otherwise right now, we do some "system" testing and "hope" things will work out - not really a "professional" approach.

Thank you again, Serge

Ken Cantu

Serge Tkachov:

Hi Ken,

Thanks for the quick reply.

There is a general problem in the Convio form development that it doesn't have a testing and staging environment.

We can develop and test how the form looks and works until the point of submitting data, but I can also test that locally on my computer too.

The two areas that I would like to see improvement on is submitting and viewing "all" entry field data so that we can confirm that data was submitted and it was submitted in correct format and second, test the generation of email responses upon submission. As a university, we have stringent rules on how the email is formatted and it needs to look formal. We also use data from the form and/or from the database on the response emails.

These improvements would help greatly in our development, otherwise right now, we do some "system" testing and "hope" things will work out - not really a "professional" approach.

Thank you again, Serge

I agree, it would be helpful. You should open a feature request case and mark it as an 'enhancement request' for this and specify out all the desired functionality. This goes directly to our product management team for review so it is a great way to get these type of ideas into the product roadmap.

For testing the email, you can use the Test Drive mode on Step 6 of editing the donation form and put in the email address to receive the autoresponder. It might not include all the custom field elements you put in the form but you can at least check all the rest of the formatting of the email without having to make a transaction.

Thanks,

Ken