-
Notifications
You must be signed in to change notification settings - Fork 19
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.
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
Report results of a test run in the status bar #90
Comments
Apoorva-GA
added a commit
to getgauge/gauge
that referenced
this issue
Feb 5, 2018
Apoorva-GA
added a commit
that referenced
this issue
Feb 5, 2018
Apoorva-GA
added a commit
to getgauge/gauge
that referenced
this issue
Feb 6, 2018
Apoorva-GA
added a commit
that referenced
this issue
Feb 6, 2018
Apoorva-GA
added a commit
to getgauge/gauge
that referenced
this issue
Feb 6, 2018
Apoorva-GA
added a commit
that referenced
this issue
Feb 7, 2018
Apoorva-GA
added a commit
to getgauge/gauge
that referenced
this issue
Feb 9, 2018
Apoorva-GA
added a commit
to getgauge/gauge
that referenced
this issue
Feb 9, 2018
Apoorva-GA
added a commit
that referenced
this issue
Feb 9, 2018
BugDiver
pushed a commit
that referenced
this issue
Feb 12, 2018
BugDiver
pushed a commit
to getgauge/gauge
that referenced
this issue
Feb 12, 2018
Fix should be available in gauge and gauge-vscode nightly >= 12/02/18 |
Test cases
OS
Issues
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whenever specifications are run using commands like "Run All Specifications", "Run Scenario" etc from command palette or the code lenses.
Summarize the as follows
22/P, 0/F, 0/S
where 22 is the number of scenarios passed, 0 is the number of scenarios failed, 0 is the number of scenarios skipped22/P
as green0/F
as red and0/s
as yellowOn clicking the status bar it must open the command palette with the options
The text was updated successfully, but these errors were encountered: