Skip to main content
CiviCRM

Return to Question

edited body
Source Link
sunyata
sunyata
  • 247
  • 1
  • 7

I'm pretty new to the CiviCRM world and am just finishing my first project using it. We are now in the process of making sure that our membership signup procedure (with contributions) works well. As I see it there are a couple of ways to increase the chance that we will have a high quality in this part of our system:

  1. We can communicate with users who have used the live system
  2. We can carefully monitor the stats for new users
  3. We can run tests ourselves

For the tests I see several possible ways, for example we can use the payment processor that we are using for the live payments but instead run it in test mode ("preview" in the url params). KarinG suggested in her answer to this question that we create a new payment processor and run it in live mode but with test credentials. Also there is the "dummy payment processor" which seems to be recommended in the CiviCRM user guide ("For the purposed of testing, you can configure dummy payment processors.")

How do we (in general) assureensure that our donation procedure is working well? And a more specific question: Which of the options above (dummy payment processor etc) is the best way to test a membership system?

Grateful for help and with kind regards, Tord

I'm pretty new to the CiviCRM world and am just finishing my first project using it. We are now in the process of making sure that our membership signup procedure (with contributions) works well. As I see it there are a couple of ways to increase the chance that we will have a high quality in this part of our system:

  1. We can communicate with users who have used the live system
  2. We can carefully monitor the stats for new users
  3. We can run tests ourselves

For the tests I see several possible ways, for example we can use the payment processor that we are using for the live payments but instead run it in test mode ("preview" in the url params). KarinG suggested in her answer to this question that we create a new payment processor and run it in live mode but with test credentials. Also there is the "dummy payment processor" which seems to be recommended in the CiviCRM user guide ("For the purposed of testing, you can configure dummy payment processors.")

How do we (in general) assure that our donation procedure is working well? And a more specific question: Which of the options above (dummy payment processor etc) is the best way to test a membership system?

Grateful for help and with kind regards, Tord

I'm pretty new to the CiviCRM world and am just finishing my first project using it. We are now in the process of making sure that our membership signup procedure (with contributions) works well. As I see it there are a couple of ways to increase the chance that we will have a high quality in this part of our system:

  1. We can communicate with users who have used the live system
  2. We can carefully monitor the stats for new users
  3. We can run tests ourselves

For the tests I see several possible ways, for example we can use the payment processor that we are using for the live payments but instead run it in test mode ("preview" in the url params). KarinG suggested in her answer to this question that we create a new payment processor and run it in live mode but with test credentials. Also there is the "dummy payment processor" which seems to be recommended in the CiviCRM user guide ("For the purposed of testing, you can configure dummy payment processors.")

How do we (in general) ensure that our donation procedure is working well? And a more specific question: Which of the options above (dummy payment processor etc) is the best way to test a membership system?

Grateful for help and with kind regards, Tord

Source Link
sunyata
sunyata
  • 247
  • 1
  • 7

Quality assurance considerations for membership signups

I'm pretty new to the CiviCRM world and am just finishing my first project using it. We are now in the process of making sure that our membership signup procedure (with contributions) works well. As I see it there are a couple of ways to increase the chance that we will have a high quality in this part of our system:

  1. We can communicate with users who have used the live system
  2. We can carefully monitor the stats for new users
  3. We can run tests ourselves

For the tests I see several possible ways, for example we can use the payment processor that we are using for the live payments but instead run it in test mode ("preview" in the url params). KarinG suggested in her answer to this question that we create a new payment processor and run it in live mode but with test credentials. Also there is the "dummy payment processor" which seems to be recommended in the CiviCRM user guide ("For the purposed of testing, you can configure dummy payment processors.")

How do we (in general) assure that our donation procedure is working well? And a more specific question: Which of the options above (dummy payment processor etc) is the best way to test a membership system?

Grateful for help and with kind regards, Tord