You can specify the username and password attributes on each environment in your
madcow-config.xml. For example:
This will use the username “test” and the password “p4ssw0rd” when prompted to upon opening the
Alternatively you can try inlining that information using URL conventions…
If the website being redirected to has a non-supported certificate then you’ll need to import the certificate into your local Java JDK using keytool.
The default keychain password is ‘changeit’
To add single line comment to a test simply prepend a # to the front of the line.
Comments are useful for explaining what the test is doing.
By simply running…
you can see the madcow version you used to run against. It is also included in the footer of each of the madcow test results pages.
As of writing this version 2.33 was the recommended version that Madcow 2.0 would prefer to use.
As well as producing a beautiful madcow-report showing test execution steps. Madcow also produces a industry standard junit xml and html report. Simply setup your Continuous Integration (CI) build server to execute something along the lines of: (depending on your build tool’s OS)
which will run all the tests against the configured DEV environment in your madcow-config.xml.
Then you have to simply point your CI build tool to look for junit style test results in the
/results/junit-report/ folder and you will get beautiful test result build server integration.
Probably a good idea to get that whole results directory archived with each build too, to ensure you keep copies of the details madcow results as well!
Great because Madcow 2.0 is fully open source under the Apache 2.0 License!
So simply head over to our github page. http://www.github.com/4impact/madcow or hit us up on facebook! All contributions are welcome!