ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@apache.org>
Subject Re: Plugins in tests
Date Fri, 28 Jul 2017 12:00:40 GMT
TestPlatformPlugin is only needed for .NET tests.
I would gladly move it somewhere else, just not sure how to do this
properly, because .NET uses ignite-core only.
Any advice? Create a new module?

Pavel

On Fri, Jul 28, 2017 at 2:57 PM, Yakov Zhdanov <yzhdanov@apache.org> wrote:

> Hello!
>
> I see this output in each test I run:
>
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
> Configured plugins:
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
>   ^-- TestPlatformPlugin 1.0
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
>   ^-- -
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
>   ^-- TestReconnectPlugin 1.0
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
>   ^--
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
>   ^-- StanByClusterTestProvider 1.0
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
>   ^-- null
> [2017-07-28 14:43:58,648][INFO
> ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][
> IgnitePluginProcessor]
>
> I see that plugins were added by D. Karachentsev, P. Tupitsyn and D.
> Govorukhin. Guys, are these plugins required for each test we run? I doubt
> if it is true. Can we move them to another module similar to p2p classes
> and plug them in only when required? Otherwise they are always in class
> path and always activated which alters default Ignite configuration in
> which we have no any plugin configured.
>
> Thoughts?
>
> --Yakov
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message