Isolated environment for tests suite

[matthieucan]

Hi, [I hope you don't mind using the issues tracker for wishlist-related items, but as this one requires further discussion I thought it would be better] I think the tests suite should run in an isolated environment for these 2 main reasons:

• side-effects: tests which http-POST have side-effects which affect the dev instance, for example misc/preferences modifies /etc/adagios/userdata/.
• tests involving hosts and services should have access to a normalised set of pre-configured hosts, to test the correct display of their information.

What I further suggest:

• use a settings_tests.py, which imports settings.py and overrides pertinent values.
• have a testdata/ folder, which provides user data, a replacement for /etc/adagios, and something like a fake livestatus endpoint (no idea if the latter is possible, but it would be really great).

What do you think?

[palli]

What I further suggest: use a settings_tests.py, which imports settings.py and overrides pertinent values.

Not a bad idea. adagios.conf actually does this already, but might need some modifications so it fits the testing better.

and something like a fake livestatus endpoint

The same idea floated in the pynag project, and now there is a pynag.Utils.misc.FakeNagiosEnvironment which starts up an isolated instance of nagios+configs+livestatus. This could be really handy inside adagios as well. I'll see if i can cook something up.

[matthieucan]

Wow awesome! Gonna have fun with this :smiley:

[matthieucan]

Thank you very much!

[palli]

I think it is safe to close this issue for now, the configuration used in the isolated environment is very minimal as is. But as need arises in the future we can add hosts/service. (for example use dataset01 directoy in pynag/tests/)

[matthieucan]

Alright!