This issue works as an index to track and discuss progress on implementing more tests in the module.

These tasks are tagged with a "Needs tests" tag.

Some tasks against Twitter API do not need OAuth, hence the following classification:

Investigation prior to implement tests:

Without using OAuth:

With OAuth:

Comments

juampynr’s picture

Issue summary: View changes

Added task.

juampynr’s picture

Issue summary: View changes

Added task.

juampynr’s picture

Issue summary: View changes

Added a task.

juampynr’s picture

Issue summary: View changes

Added a task.

juampynr’s picture

Issue summary: View changes

Added a task

juampynr’s picture

Issue summary: View changes

Added a task.

juampynr’s picture

Issue summary: View changes

Added issue to test runkit

juampynr’s picture

Issue summary: View changes

Fixed typo in HTML.

David Hernández’s picture

In the issue #1346790: Change hardcoded host to use a drupal variable I've updated the hardcoded host in the Twitter class to use a Drupal variable, to make easy to do tests.

juampynr’s picture

Moved to 7.x branch.

juampynr’s picture

Version: 6.x-3.x-dev » 7.x-3.x-dev

Doh! Now actually moving to 7.x branch.

juampynr’s picture

Title: Add tests to simulate main use cases » Testing Roadmap

Updated title.

xurizaemon’s picture

http://drupal.org/files/uc_dps_pxpay.test from #1807242: Test checkout with PXPay demonstrates one way of doing a couple of steps required for this -

* Allowing us to test Twitter logins without sharing the username/password details (you define the login in settings.php or by editing the .test file)
* Submitting secret details (test CC data in the issue above, twitter user/pass for this issue) to a remote site and being redirected back

juampynr’s picture

Status: Active » Closed (won't fix)

Obsolete. Closing.

juampynr’s picture

Issue summary: View changes

Added task