Open aledsage opened 12 years ago
On the brooklyn-dev mailing list, Alex posted the following:
Looks great!
Maybe first do a starter test which creates a simpler app (just an as7, and one with just a tomcat for jmx testing) and soaks it -- to make no leaks in collecting sensors.
Optional extension with pings the web console to make sure no leaks there.
If fixture (and web-check extension) are easily reusable that's a big plus of course!
We need more longevity and stress tests in Brooklyn.
Example test As a first test to write, how about:
We'd programmatically monitor:
ps aux | grep jboss
returns different pids over time)If watching manually, we'd also run jconsole.
We'd first run this on localhost. Then we'd run it with a fixed set of IPs if we have access to a few spare servers.
Test structure As a first step, we can write a script that launches both brooklyn and a "monitoring process" to do the above checks. Groovy is probably a good bet for the monitoring process code, because it is scripting.
As a future step, we would beg a server (or few) for running this regularly. We'd have jenkins run a testng test for it (that called the scripts?). Jenkins would run it every day, and the test would run for 23 hours.
Improving test coverage There are various other things I'd love to be covered in the longevity tests. These include: