Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I want to create Simpletest tests for these modules but am unsure of the best way to accomplish it as it uses 3rd party services.
My first thought was just to link it to you account info that you have setup normally so that the tests will run as whoever is running the tests on their AWS accounts. However, I am unsure about this approach.
Would these tests be sufficient? What if people don't have accounts with those services? Does it matter?
To do a full round of testing, we would have to transfer data to and from services which cost money. Is this ok? Should just put a disclaimer?
Then when it comes to services like FPS (Flexible Payment Service) do we actually perform transactions?
I would like to hear developers thoughts on how to accomplish this. Does anyone know of a free testing ground that all the services work on but don't charge for?
Comments
Comment #1
toemaz commentedI have no experience with simple testing procedures or standards.
It might matter. But I don't know how far you need to go. For S3 and SQS, my only test consists out of requesting the available buckets and queues. I store the returning list in an array variable (set_variable) which can be used by other modules.
I do think it any testing might be useful. Perhaps it can be even added to the cron so it can be polled any xx hours. It would hurt my website service if any aws service falls out, so if I could be notified by email, this would be nice.
Just a disclaimer should be fine I guess. The cost will be trivial anyway.
There is a sandbox most likely. Haven't test this one.
No idea.
Comment #2
davisben