On Fri, 31 Oct 2014, Rainer Gerhards wrote:
What we don't have is these unit tests. Well... a handful exists, but I stopped that route as it didn't really work out. One problem is that rsyslog is very modular. So if you want to test any function that really does work, you need to link in and activate a lot of the rsyslog runtime. In true isolation, only tiny functions can be tested.
I was wondering about that. The core runtime creates a lot of infrastructure that the modules make use of, so it's hard to test a module without dragging in most of the core.
and the complexity of the core can at least minimized, if not disabled. Is it possible to define the main queue to be 'Direct'?, if so, a config that had a socket as the input with a direct queue to one module as the output (or a module as the input with a direct queue to a file output) becomes about as straightforward as you would have if there was a dedicated test harness to try and rule the modules without the core.
David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
