auxesis-cucumber-nagios 0.2.1 → 0.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README.md +27 -16
- data/bin/cucumber-nagios-gen +0 -0
- data/cucumber-nagios.gemspec +1 -1
- metadata +1 -1
data/README.md
CHANGED
|
@@ -1,23 +1,36 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
1
|
+
cucumber-nagios
|
|
2
|
+
===============
|
|
3
3
|
|
|
4
|
-
-
|
|
5
|
-
|
|
6
|
-
- rubygems
|
|
4
|
+
cucumber-nagios allows you to write high-level behavioural tests of web
|
|
5
|
+
application, and plug the results into Nagios.
|
|
7
6
|
|
|
7
|
+
As Bradley Taylor [put it](http://bradley.is/post/82649218/testing-dash-metrics-with-cucumber):
|
|
8
8
|
|
|
9
|
-
|
|
10
|
-
|
|
9
|
+
“Instead of writing boring monitoring plugins from scratch,
|
|
10
|
+
you can now do behavior driven ops!
|
|
11
11
|
|
|
12
|
-
|
|
12
|
+
Transform from a grumpy, misanthropic sysadmin to a hipster,
|
|
13
|
+
agile developer instantly.”
|
|
13
14
|
|
|
14
|
-
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
Setting up a project
|
|
18
|
+
====================
|
|
19
|
+
|
|
20
|
+
To set up a standalone cucumber-nagios project, run:
|
|
21
|
+
|
|
22
|
+
cucumber-nagios-gen project <project-name>
|
|
23
|
+
|
|
24
|
+
This will spit out a bunch of files in the directory specified as <project-name>.
|
|
25
|
+
|
|
26
|
+
Check the README within this directory for specific instructions for managing
|
|
27
|
+
the project.
|
|
15
28
|
|
|
16
29
|
|
|
17
30
|
Writing Features
|
|
18
31
|
================
|
|
19
32
|
|
|
20
|
-
I suggest you put your features under under features/$fqdn/$name.feature.
|
|
33
|
+
Within your project, I suggest you put your features under under features/$fqdn/$name.feature.
|
|
21
34
|
|
|
22
35
|
You'll want to have a read of the Cucumber documentation, however
|
|
23
36
|
your tests will look something like this:
|
|
@@ -71,7 +84,7 @@ Running
|
|
|
71
84
|
|
|
72
85
|
Invoke the cucumber feature with the cucumber-nagios script:
|
|
73
86
|
|
|
74
|
-
bin/cucumber-nagios features/
|
|
87
|
+
bin/cucumber-nagios features/smh.com.au/smh.feature
|
|
75
88
|
|
|
76
89
|
cucumber-nagios can be run from anywhere:
|
|
77
90
|
|
|
@@ -79,15 +92,13 @@ cucumber-nagios can be run from anywhere:
|
|
|
79
92
|
|
|
80
93
|
It should return a standard Nagios-formatted response string:
|
|
81
94
|
|
|
82
|
-
Critical: 0, Warning: 0, 2 okay |
|
|
95
|
+
Critical: 0, Warning: 0, 2 okay | passed=2, failed=0.0, total=2
|
|
83
96
|
|
|
84
97
|
Steps that fail will show up in the "Critical" total, and steps that pass
|
|
85
98
|
show up in the "okay" total.
|
|
86
99
|
|
|
87
|
-
The value printed at the end is
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
Critical: 1, Warning: 0, 2 okay | value=2.000000;;;;
|
|
100
|
+
The value printed at the end is in Nagios's Performance Data format, so it
|
|
101
|
+
can be graphed and the like.
|
|
91
102
|
|
|
92
103
|
|
|
93
104
|
Caveats
|
data/bin/cucumber-nagios-gen
CHANGED
|
File without changes
|
data/cucumber-nagios.gemspec
CHANGED