Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-19819

Incorporate iATS tests into core tests as much as possible

    Details

    • Type: Improvement
    • Status: Won't Do
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: 4.7.14
    • Fix Version/s: 4.7.17
    • Component/s: None
    • Labels:
      None
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)
    • Documentation Required?:
      None
    • Funding Source:
      Contributed Code
    • Verified?:
      No

      Description

      Examine iATS test suite maintained by KarinG at https://github.com/iATSPayments/com.iatspayments.civicrm#testing and create a test in core for each one as much as possible.

      Tim Otten and Coleman Watts in the absence of Eileen McNaughton can you
      1) Confirm that testing of iATS extension for payment processing in core is Okay (cf CRM-19799), and that test suite should call to install and enable this extension?
      2) Recommend an approach to screen scraping (perhaps just regular Selenium) to automate steps 6 and 7?
      3) Suggest an approach to creating a special test job that will complete a test after a long delay in order to handle steps 9 and 10.

      Should we make a parallel set of tests for a non-iATS payment processor like PayPal Pro?

      Document here in issue description which tests have been and have not been implemented.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pradeep.nayak Pradeep Nayak
                Reporter:
                joemurray Joe Murray
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: