Hi crystaldawn,

We spoke earlier about adding some tests to uc_ssl. To get an idea of the scope of this, I looked at the tests in the secure pages module and will summarize them here.

  • Test that HTTPS is enabled on all admin, node edit, user, user login, and autocomplete paths.
  • Test compatibility with locale module
  • Test all HTTP/HTTPS redirecting
  • Test form submissions with HTTP/HTTPS
  • Test user login
  • Test page caching compatibility
  • Test redirects on aliased paths
  • Test against open redirects (not 100% I understand what this one means)
  • Test role based switching (not 100% sure uc_ssl needs this)

In terms of lines of code, secure pages' test file is ~ 360 lines of code. Considering some of these functions will not be necessary in uc_ssl, it may be possible to get the tests done in 300 lines or less (barring any functional differences in this module that requires more complex testing requirements).

One final note: It appears that secure pages runs all of these tests through one main function as opposed to keeping them discretized. I know that provides a speed benefit in terms of the length of time to run the tests, but I'll leave that up to discussion whether we want to take a similar approach. It seems like it would introduce issues instead of keeping them as true unit tests.