Add in-depth testing of sites to ddev tests

[rfay]

What happened (or feature request):

In our tests we have a variety of CMSs that we install and start ddev.... but we don't actually do anything with the sites after starting, just test ddev functions like import-db and the like. For real test coverage we need to verify:

• Hitting the front page works
• Logging in works
• Visiting some important URLs works
• Imagecache/image styles or the equivalent work properly

We'll need to add to this list as we go.

What you expected to happen:

How to reproduce this:

Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.

Anything else do we need to know:

Related source links or issues:

Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)

[cweagans]

I've been using https://github.com/headzoo/surf on a personal project with a decent amount of success. Might be useful here.

[rickmanelius]

I'm not sure if this was already addressed in #671. Seems useful and will pin to v1.2.0 as a milestone related to CMS support.

[rfay]

No, this was a spin-off from #671 - We've never had any nontrivial tests for the test sites we install, and it will really improve our coverage and detection when we add them.

[rfay]

These should probably be spun off into separate tickets.

When doing Wordpress, please work closely with @alkymst to do something reasonable there.

[rfay]

So the way I'm thinking about this now is pretty easy to implement.

1. After Provide access to router within web container by hostname, fixes #842 #1151 lands, it adds a URI+Expectation.
2. Add a non-static expectation URL (or array of expectations?) to the TestSite type
3. In TestDdevImportDB, test appropriate expected URLs for each project.

I think that's all we really have to do. Not very ambitious at all.