DEdelbel·Aug 17, 2015
Like Gherkins? https://github.com/cucumber/cucumber/wiki/Gherkin
In Ask HN: Why did literate programming not catch on?cucumber
common
OPEN SOURCE2011–2015
cucumber / common
common
A home for issues that are common to multiple cucumber repositories
5Distinct people
5Mentions
0Explicit recommenders
3.4KGitHub stars
What to know before exploring
What it is
A home for issues that are common to multiple cucumber repositories
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:03:30 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year5 dated mentions
Observed mentions: 2011-06-17 18:16:48 UTC to 2015-08-17 06:45:17 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 3 | 2 | 1 |
What Hacker News says
3 sourcesAsk HN: Better way to write specs?
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
Read the rest
achine
And I have deposited 1$
When I press the coffee button
Then I should be served a coffee
Scenario: VIP buys coffee
Given there are 1 coffees left in the machine
And I have deposited 1$
And I am on the VIP guest list
When I press the coffee button
Then I should be served a coffee
Then my money should be returned
.. scenario for VIP trying to buy coffee, but no coffee left
.. scenario for regular user trying to buy coffee, but no coffee left, etc.
(example from: https://github.com/cucumber/cucumber/wiki/Feature-Introduction)
The “Funny” internationalization languages could be doing more harm than good
1 points · Open discussion