here's the code that's trying to configure it:
https://github.com/jstrachan/fuse/blob/work/fabric/fabric-camel-autotest/src/main/java/io/fabric8/camel/autotest/CamelAutoTestService.java#L112-112

try add the camel-example-autotest profile when provisioning the camel-quickstarts-cbr or camel-example-wiki and you'll see it try to auto-send example messages from the wiki:
https://github.com/jstrachan/fuse/tree/work/fabric/fabric8-karaf/src/main/resources/distro/fabric/import/fabric/configs/versions/1.0/profiles/example-camel-autotest/testMessages

in that folder, there's a folder for each camel context ID, then a child folder for each route ID

By default the mocking of inputs/outputs is enabled - you can turn it on and off via the Configuration UI on the Profile page (selecting the Fabric8 Camel Auto Tester PID to view the form).

Incidentally the main use case for stubbing out the real endpoints; is so that we can always send into the input (some endpoints, like timers, don't allow this and barf) - and some endpoints can't be browsed. So while you can make use of camel-autotest if you use, say, seda/amq inputs and outputs - for many other kinds of endpoints you can't send into them or browse the output