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.

Sign up for GitHub

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

Jump to bottom

Progress formatter (CLI) #16

Closed
jbpros opened this issue Jun 5, 2011 · 1 comment
Closed

Progress formatter (CLI) #16

jbpros opened this issue Jun 5, 2011 · 1 comment
Assignees
@jbpros
Milestone
0.1

Comments

@jbpros
Copy link
Member

jbpros commented Jun 5, 2011

Currently, cucumber.js CLI uses a bare "pretty" formatter to output results. It displays the source of the feature while it is running. It is too verbose and does not include any summary.

By default, CLI must use a progress formatter that outputs things in a similar fashion than its Ruby brother (dots and chars to indicate step execution results).
@ghost ghost assigned jbpros Jun 5, 2011
jbpros added a commit that referenced this issue Jul 5, 2011
@jbpros
Integrate new core feature running through Cucumber.rb and Aruba
f3b40fd 
- Progress formatter is under development (issues #16, #17)
- core.feature first scenario is passing

Squashed commit of the following:

commit ed3db19c77f40107b3a2038ace8267d4cb642e85
Author: Julien Biezemans <[email protected]>
Date:   Tue Jul 5 23:46:07 2011 +0200

    Make progress formatter handle failing steps

commit 998dc26bc327876d23c4e7fdc2526a133659db99
Author: Julien Biezemans <[email protected]>
Date:   Tue Jul 5 23:00:52 2011 +0200

    Assert cucumber.js succeeds on passing scenario

commit 852c214c61c36077e70c0a11d8f4bf06ff685f0b
Author: Julien Biezemans <[email protected]>
Date:   Tue Jul 5 22:49:20 2011 +0200

    Integrate new core feature running through Cucumber.rb and Aruba

commit 75b82ed9317304a0ed9f3b8c56c3b2c0ae35caa9
Merge: 749512a b5ff2a7
Author: Julien Biezemans <[email protected]>
Date:   Tue Jul 5 21:15:56 2011 +0200

    Merge branch 'aruba-new-core-local' into 16-progress_formatter

commit 749512a4aa652dd8eac39e133427e2a26156bae1
Author: Julien Biezemans <[email protected]>
Date:   Tue Jul 5 18:59:51 2011 +0200

    Add a scenario for failing steps

    On hold because failing steps are not yet handled

commit 4bcd476544e4c094e9862fcf209c7a2446d63a8b
Author: Julien Biezemans <[email protected]>
Date:   Tue Jul 5 16:45:45 2011 +0200

    Handle multi-scenario features

commit b5ff2a7d12519a8434b14b4380a6662880bb798c
Author: Julien Biezemans <[email protected]>
Date:   Tue Jul 5 11:18:51 2011 +0200

    WIP

commit acecc9acf8c547bcaffd1e827247ad66c4562947
Author: Julien Biezemans <[email protected]>
Date:   Tue Jul 5 11:05:29 2011 +0200

    Fix CucumberJsMappings module name

commit afe3460dea101c2b6306a1ceb62a6354bb2773f8
Author: Julien Biezemans <[email protected]>
Date:   Wed Jun 29 00:16:55 2011 +0200

    Make first new core scenario pass with Aruba

    JS mappings are not semantically correct yet. e.g. cucumber.js cannot run specific scenarios at the moment; this prevents us from implementing run_scenario() the same way as within ruby mappings.

    To run it:
        $ ARUBA_REPORT_DIR=doc cucumber features/cucumber-features/core.feature:16 -r features ; open doc/features/cucumber-features/core.feature\:16.html

commit 87d27c739fea70fc4783737f35b6a6f137eb76f9
Author: Julien Biezemans <[email protected]>
Date:   Sun Jun 19 22:21:26 2011 +0200

    Count passed steps and scenarios in progress formatter (wip)

commit 15d749bac0f6956646df65b1fdf8e92cfbd62b8f
Author: Julien Biezemans <[email protected]>
Date:   Sun Jun 19 11:48:38 2011 +0200

    Add initial working progress formatter

commit dc3301a5148b8737cf838b7435e6aac8e797bc14
Author: Julien Biezemans <[email protected]>
Date:   Thu Jun 16 23:16:13 2011 +0200

    Handle step result (wip)

commit f5f6268714a6310cfeaf2c6ed9445c1921053eca
Merge: 0947988 8ae4c0e
Author: Julien Biezemans <[email protected]>
Date:   Wed Jun 15 00:37:15 2011 +0200

    Merge branch 'master' into 16-progress_formatter

commit 0947988a580714856b1d551ee9acdcc9ddc15a9f
Merge: 7f595b4 252634f
Author: Julien Biezemans <[email protected]>
Date:   Wed Jun 15 00:30:04 2011 +0200

    Merge branch 'master' into 16-progress_formatter

commit 7f595b48713b352042d2c382e19841957cd42b76
Author: Julien Biezemans <[email protected]>
Date:   Wed Jun 15 00:19:31 2011 +0200

    Add ProgressFormatter.listen()

commit a08b10b557e90e0f6ef3cdcb96558b7c45a6daf5
Merge: 0857a6c fc83930
Author: Julien Biezemans <[email protected]>
Date:   Tue Jun 14 19:20:56 2011 +0200

    Merge branch 'master' into 16-progress_formatter

    Conflicts:
    	lib/cucumber.js

commit 0857a6c
Author: Julien Biezemans <[email protected]>
Date:   Mon Jun 6 15:52:28 2011 +0200

    Stuck because of 'after' events fired too late -- on hold until refactoring is finished
jbpros added a commit that referenced this issue Jul 21, 2011
@jbpros
Handle failures and add 'progress' formatter (close #6, #16, #17)
f600027 
- Failing steps are now properly handled and following steps in scenario are skipped
- Second core.feature scenario is passing
- Progress formatter is now available and used by default
- We still miss stack trace output on failure
@jbpros jbpros closed this as completed Jul 21, 2011
@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jbpros jbpros

Labels
None yet
Projects
None yet
Milestone
0.1
Development

No branches or pull requests
1 participant
@jbpros