From f6f23a26756228b6200fbdafa5ce8d6378644db7 Mon Sep 17 00:00:00 2001 From: Simon Pasquier Date: Wed, 25 Sep 2019 09:26:53 +0200 Subject: [PATCH] docs: update unit testing rules (#6051) * docs: update unit testing rules Signed-off-by: Simon Pasquier * More nits fixed Signed-off-by: Simon Pasquier --- docs/configuration/unit_testing_rules.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuration/unit_testing_rules.md b/docs/configuration/unit_testing_rules.md index 2d1e4ffdc..f2bbbb664 100644 --- a/docs/configuration/unit_testing_rules.md +++ b/docs/configuration/unit_testing_rules.md @@ -50,7 +50,7 @@ input_series: alert_rule_test: [ - ] -# Unit tests PromQL expressions. +# Unit tests for PromQL expressions. promql_expr_test: [ - ] @@ -83,7 +83,7 @@ values: Prometheus allows you to have same alertname for different alerting rules. Hence in this unit testing, you have to list the union of all the firing alerts for the alertname under a single ``. ``` yaml -# It's the time elapsed from time=0s when the alerts have to be checked. +# The time elapsed from time=0s when the alerts have to be checked. eval_time: # Name of the alert to be tested. @@ -114,7 +114,7 @@ exp_annotations: # Expression to evaluate expr: -# It's the time elapsed from time=0s when the alerts have to be checked. +# The time elapsed from time=0s when the expression has to be evaluated. eval_time: # Expected samples at the given evaluation time. @@ -131,7 +131,7 @@ exp_samples: # go_goroutines{job="prometheus", instance="localhost:9090"} labels: -# The expected value of the promql expression. +# The expected value of the PromQL expression. value: ```