Currently, tests are designed to run with securepages disabled and admin/config/development/testing accessed via HTTP.

This is kind of a silly limitation, considering this module's purpose.

It should be straightforward to fix; all URLs in the tests just need to be explicit about 'https' => true/false.

Comments

astonvictor’s picture

astonvictor commented
Issue summary: View changes
Status: Active » Closed (outdated)

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks