Since AEM 6.0, Adobe introduced a test automation framework called Hobbes.JS that can provide functional automated tests for the AEM UI. The stock Hobbes.JS package from Adobe provides:
- A Test panel in the touch-optimized UI for running tests.
Initially, we started to develop for one of our clients an automation framework based on Hobbes.JS that would provide us valuable results within the development process. From the beginning, we saw some advantages of using the Adobe tool because some facts were already proven like:
- Integration with AEM (only in author mode)
By seeing great potential in this tool, we saw the need to have additional features like:
- Nightly automated builds using Jenkins
- Valuable test reports, that can be used to provide a Quality Assurance health check to the client for each iteration. (JUNIT, Pretty and HTML formats)
- Page objects support – an organized way to organize the CSS locators in the development files
- Slack notifications – because our team needs to be constantly informed
The Technical Datasheet
Having our feature list ready, we have started development and after a few weeks of coding we are proud to introduce: Hobbes Runner – a Node.JS application that integrates directly with Hobbes.JS, extending it’s out of the box features.
The technical aspects of our wrapper can do the following:
- Hook in the Hobbes test process and act on various test events like: Start, Stop, Pause, Finish
- Extract test reports in XML, HTML and TXT formats to feed them to an external consumer like Jenkins (JUnit plugin)
- Specify the browser that will run (Firefox, Chrome or IE)
- Various debug levels for Selenium
- The ability to run in our Selenium grid
And because a picture is worth a thousand words, check the screenshot below
Developing with Hobbes.JS
The functionality of CRXDE Lite is very well covered in the Adobe documentation here.
(!) Keep in mind that only the Author mode of AEM is supported so far in Hobbes.JS
Hobbes.JS already supports a lot of out of the box browser interactions, but if you do need something custom done, below you will find a very good example of a well written function.
Documenting you code is key in every development project, remember that!
You will need to write locators and custom functions in external files for code readability purposes.
- For locators CSS and jQuery locators we have: locators.js
- For functions we have: functions.js
These two files are loadable by Hobbes code and should always be used.
- Here is a sample of a Jenkins JUNIT report:
- Next up we have the real time running of Hobbes in action: