[Feedhenry-raincatcher] What is the plan for verifying modularity

[Paolo Haji]

We've actually started adding unit tests for some of the modules just
recently, but most of course access the underlying interfaces directly.

However if we start building a set of black-box ones that access the
functionality only through a mediator we could end up with essentially a
spec of what a user-replacement version should provide, in addition to
serving as documentation of the usage of the topics provided by the model.

Eventually mediator topics could also have some sort of schema validation
of the data, if that also helps. There are lots of limitations on what we
can do with a library to supply something that would ideally be a language
feature (c.f. angular dependency injection being so awkward as well).

On Thu, Feb 2, 2017 at 12:23 PM, Summers Pittman <supittma at redhat.com>
wrote:

> One of the goals of Raincatcher is that the loosely coupled modules can
> communicate with each other via a message bus and as long as you implement
> the handlers according to the modules spec you can "easily" replace the
> Raincatcher module with a module that provides your own implementation.
>
> Are there any tests or test plans for verifying this behavior?
>
> Right now we have the demo application which tests all the modules work
> together, but there doesn't seem to be much in the way that tests the
> modules in isolation.  More importantly, plugging in custom behavior makes
> for an awesome demo and opportunities for cross promotion with other
> projects.
>
> Summers
>
> _______________________________________________
> Feedhenry-raincatcher mailing list
> Feedhenry-raincatcher at redhat.com
> https://www.redhat.com/mailman/listinfo/feedhenry-raincatcher
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-raincatcher/attachments/20170202/096ab6ff/attachment.htm>