When building Mule architectures a company will often need to run several instances of Mule ESB: Some on QA, some on staging, and on production, perhaps some instances running locally and some others in another continent. Managing Clusters of Mule Servers, keeping track of what application is running where, and knowing what is the health of those instances at a glance, or even being warned when something wrong happens… That is Mule Enterprise Console job!
We are evaluating using Nagios or a similar Big Brother Enterprise solution for displaying information about our many Enterprise Mule instances, applications and the status of our production and staging environments. The only sure thing is that we presented a budget for buying a couple of 55” monitors and were approved. Pure awesomeness!
This is complicated.
Ok. Face the music. Let’s debug.
Check list:
What is happening here?
When your test base can be measured in tens of tests (or more) you should pay attention to bests practices and design principles if you want a highly maintainable code, quite resistant to technological changes, changes on the UI, etc. This article introduces Page Model pattern that is a great help in that regard.
Why are GUI integration tests needed? On which testing tool technology should I base my tests? What are the cost/benefit of the choosing one over the other? In this brief article we will give you a quick look at the answers to those questions.
