Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test tick scripts using node output #11

Open
gpestana opened this issue Sep 23, 2017 · 2 comments
Open

Test tick scripts using node output #11

gpestana opened this issue Sep 23, 2017 · 2 comments

Comments

@gpestana
Copy link
Owner

What

Kapacitor features node outputs, in which processed data from kapacitor can be output to a certain service. Kapacitor has two types of node output implemented out of the box and ready to use: HTTPOutputNode and InfluxOutputNode. It is also possible to define custom output nodes. TICKscripts which process data and output it to a certain endpoint may or may not trigger alerts.

It would be a great feature for kapacitor-unit to test node outputs.

Test flow:

  1. Define the test configuration (which data to load, which tick script to load, what are the output expected after the data processing)
  2. Load tick script
  3. Load task
  4. Inspect output data
  5. Compare expected data with output data

Open points

A) How to pipe data coming from an output node to inspect its contents and compare with the expected data defined in the test definition?
kapacitor-unit should be able to consume processed data coming from any type of NodeOuput, predefined or custom.

B) How would the test definition look like?

C) Add way to split configuration tests so that it's easier to manage them? (e.g. to have a test configuration for alerts and another for data processing (OutputNode) type of tests.

@smolse
Copy link

smolse commented Sep 25, 2017

There is also HTTPPostNode whose output might need to be tested.

@vlaurenzano
Copy link
Contributor

I am currently working on changes that will allow for out node testing. I'm starting with the log node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants