<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hi Michael,</div><div><br></div><div>This is a great question ... thank you for raising it. </div><div><br></div><div>So you are asking about a mock resource ... or test fixture ... to facilitate integration testing of Hawkular? I think that is a great idea. In fact, I can envision a small portfolio or quiver of mock resources or test fixutres:</div><div><br></div><div><ul><li>availability up</li><li>availability down</li><li>availability unknown</li><li>generating metrics low volume</li><li>generating metrics high volume </li><li>etc ...</li><li>to cover absolutely every primary use-case & resource that Hawkular would me monitoring</li></ul><div><br></div><div>I agree if we had a set, quiver, portfolio, or inventory of test fixtures it would facilitate integration testing. </div><div><br></div><div>Next question ... might be "where"?</div><div><br></div><div><ul><li>on the JON QE Bladecenter ... </li><li>in a private Docker registry </li><ul><li>developers and QE could do a 'docker pull' and get whatever fixture they needed </li><li>this would de-couple the fixtures from the bladecenter ...and allow the test fixtures to be manipulated more easily by the developers and QE </li></ul><li>in a public Docker registry</li><ul><li>this would decouple from the bladecenter</li><li>allow developers in the community to use these test fixtures </li></ul></ul><div><br></div><div>Something I saw recently ... is this thing called Arqullian Cube ... which can be used to control the lifecycle of Docker containers as part of integration tests. Some info here ... --->> <a href="http://blog.arungupta.me/run-javaee-tests-wildfly-docker-arquillian-cube/" data-mce-href="http://blog.arungupta.me/run-javaee-tests-wildfly-docker-arquillian-cube/">http://blog.arungupta.me/run-javaee-tests-wildfly-docker-arquillian-cube/</a> So with this approach possibly ... integration tests could be written where test fixtures for availability up/down/unknown are programmatically spun up in Docker and automated integration tests run. </div><div><br></div><div>Also ... another possible approach ... is to programmatically control these test fixtures in our Bladecenter via a REST API. So we/QE built a REST API to wrap the RHEV/Foreman infrastructure in our Bladecenter. So anything that can be done thru the UI can be done programmatically. So you can imagine an integration test for availability... where in @BeforeClass ... the automated test makes a REST call to spin up ...say ... an availability unknown test fixture ...and some tests run. </div><div><br></div><div>Let's please talk more about this. I would like to learn more about your mock site idea where the availability state changes on a schedule. I'll set up a Bluejeans time and an etherpad where we can discuss this ...requirements, approaches, use-cases, etc .... </div><div><br></div><div>Regards,</div><div><br></div><div>Michael Foley</div><div>JON and Lumbini QE Supervisor </div><div><br></div><div><br></div></div></div><div><br></div><div><br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"mike thompson" <mithomps@redhat.com><br><b>To: </b>"Discussions around Hawkular development" <Hawkular-dev@lists.jboss.org><br><b>Cc: </b>"Michael Foley" <mfoley@redhat.com>, "Armine Hovsepyan" <ahovsepy@redhat.com><br><b>Sent: </b>Thursday, April 9, 2015 10:24:45 PM<br><b>Subject: </b>Ways to Test Availability Down?<br><div><br></div>I guess this question is mainly targeted to Hawkular QE. So all of my testing (especially on a dev box) shows availability 100% (as most sites will). So while I can mock this in code to show downtime and unknown. It appears that we need a consistent way to demonstrate up/down/unknown/whatever else. Is there a QE way to do this currently?<br><div><br></div>I’m thinking a mock site that changes states every 5 or 10 minutes that is publicly available. This way we could all link our integration tests to this site to provide full coverage of states(and there could be other availability states like I have mentioned in other Hawkular ML mails).<br><div><br></div>The use case I want to add is as a developer I want to test all availability states within a half hour (or whatever timeframe, but as everything waits on tests passing less is better) by pulling in certain site(s).<br><div><br></div>Ideas?<br><div><br></div>— Mike T<br><div><br></div></div><div><br></div></div></body></html>