If the manager user and password are not specified in the configuration for the managed Tomcat adapter, the adapter should automatically add a manager user for the duration of the test run.

After all, the managed Tomcat adapter knows the location of the Tomcat installation and is controlling its lifecycle. We shouldn't require the developer to setup a manager user when the adapter could handle it (assuming it has the necessary permissions, but then we can say we tried). This is especially important if Tomcat is being automatically downloaded and extracted as part of the test execution.

I'm open to having a property to control this behavior, something like "autoCreateManagerUser".

Here's what would be added to tomcat-users.xml for Tomcat 7

<role rolename="manager-script"/>
<user username="arquillian" password="arquillian" roles="manager-script"/>