common

Like Gherkins? https://github.com/cucumber/cucumber/wiki/Gherkin

Is there a standard way of writing BDD specs in a rule-based format? To me, the traditional Gherkin-style format is too verbose and depends on defining edge-cases in lengthy scenarios. I'm looking for something that more defines the business logic in English and covers the edge cases in the test code. Like: Feature: Serve coffee Rule: If there is no coffee left, refund the money Otherwise: Rule: Coffee should not be served until paid for and until the button has been pressed Rule: If the customer is on the VIP list, don't charge any money Instead of: Feature: Serve coffee Coffee should not be served until paid for Coffee should not be served until the button has been pressed If there is no coffee left then money should be refunded Scenario: Buy last coffee Given there are 1 coffees left in the m

> but seriously, does nobody else see a problem with your monitoring configuration being hosted on the site being monitored? So, if the file is unreachable, something is probably very very wrong. Malicious changing of the file could be addressed by firing an alarm when the file changes. > It is a bit like asking a hospital patient to keep an eye on his own charts and to let you know if anything goes wrong .. No, it's a bit like leaving the chart with the patient, trusting that he won't destroy it. > do people really switch monitoring companies often enough to justify having a standard configuration format? Do people really switch monitoring companies rarely enough to justify keeping a myriad of incompatible configuration formats? This also has the benefit of you owning all of your own data. > ps. cucumber syntax is horrible because it per

If you're as confused as I am, "cucumber", in this case, is referring to a testing framework for ruby, not a vegetable. https://github.com/cucumber/cucumber/wiki/ a side note: am I just totally out of touch with things? "Fructose", "Cucumber", "Coffeescript", "V8"?