[WIP] add webtests, first try frontend test

[ElectricMaxxx]

Q	A
Bug fix?	maybe
New feature?	no
BC breaks?	no
Deprecations?	no
Tests pass?	no
Fixed tickets	#230, parts of symfony-cmf/symfony-cmf-docs#444
License	MIT
Doc PR	need to be created

Please do not be confused, but i try to understand that Prefix/Candidates thing. To do that i (re-)activated the frontend test, do not know why they where not active. Then i created some routes, i just wanna play how idPrefix, staticPrefixand the candidates work together.

I got an issue with instantiating the database for the test - hope not to have it in travis.

[ElectricMaxxx]

@wouterj, you know a difference in configuring the testing environment - the persistence in general? Got the same error localy. That can be the reason why web test are deactivated :-) but deactivating is no solution i think.

[ElectricMaxxx]

seems to have problems to create the database:

PHPCR\RepositoryException: Unexpected error talking to the backend: An exception occurred while executing 'SELECT 1 FROM phpcr_workspaces WHERE name = ?' with params ["default"]:

got the same issue localy. Even if i try to intit by hand.

[ElectricMaxxx]

In the last test you see my problem i wanted to show in #230 if i set an idPrefix on a document and getPath() is called everything is fine, but if i don't set it and call getPath() i got the exception (should be seen on travis).

Problem is: getPath() is called in almost every situation. The easiest is: RouteAdmin with the mapped form field path. So if i do not set any idPrefix i got that exception. Do i really need to set that prefix? Why not using the way that bundle used to work as default:
routes_basepath (admin_basepath now) removed from id is the path?

[ElectricMaxxx]

This would be a use case where i would need a "stroke" function in github. All symfony-cmf base Route instances implements the PrefixInterface which trigger an update on the property by an listener. OK, so the tests are useless/non-sense.

[dbu]

your unit tests do not persist so the prefix things can indeed be tested that way. and i think it makes sense to test them.

i guess the web tests fail because the configuration for the route_basepaths is not set to /tests but at the default /cms/routes?

[dbu]

#276 did activate the web test cases. @ElectricMaxxx would you mind rebasing and cleaning this up if there are relevant things left to do in this PR?