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.

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

add support to print list of implemented steps #2433

Merged
merged 3 commits into from
May 7, 2024
Merged

Conversation

sriv
Copy link
Member

@sriv sriv commented Nov 14, 2023

usage: gauge list --steps

fixes #2432

Signed-off-by: sriv srikanth.ddit@gmail.com

Copy link
Contributor

Benchmark Results

java_simple_serial.csv

Commit CPU Memory Time ExitCode
77e1343 32% 61496 0:20.52 0
523c400 33% 63508 0:20.32 0
9b96118 25% 63568 0:16.12 0
eead0b1 32% 65472 0:17.01 0

java_gradle_serial.csv

Commit CPU Memory Time ExitCode
77e1343 6% 94364 0:40.44 0
523c400 6% 121532 0:45.13 0
9b96118 6% 96004 0:42.09 0
eead0b1 6% 96192 0:31.32 0

java_maven_parallel.csv

Commit CPU Memory Time ExitCode
77e1343 35% 179656 0:34.40 0
523c400 33% 182012 0:32.36 0
9b96118 36% 193468 0:31.56 0
eead0b1 42% 237416 0:31.56 0

java_gradle_parallel.csv

Commit CPU Memory Time ExitCode
77e1343 5% 122608 0:46.91 0
523c400 5% 125048 0:37.07 0
9b96118 5% 124252 0:39.01 0
eead0b1 5% 115400 0:44.12 0

java_simple_parallel.csv

Commit CPU Memory Time ExitCode
77e1343 22% 63788 0:28.84 0
523c400 20% 65628 0:21.50 0
9b96118 20% 65668 0:27.20 0
eead0b1 23% 71984 0:23.81 0

java_maven_serial.csv

Commit CPU Memory Time ExitCode
77e1343 53% 198284 0:29.23 0
523c400 51% 205508 0:32.16 0
9b96118 40% 201760 0:33.93 0
eead0b1 75% 238976 0:20.09 0

java_maven_multithreaded.csv

Commit CPU Memory Time ExitCode
77e1343 44% 181400 0:32.12 0
523c400 49% 186688 0:22.21 0
9b96118 41% 178280 0:29.67 0
eead0b1 66% 242792 0:16.94 0

java_gradle_multithreaded.csv

Commit CPU Memory Time ExitCode
77e1343 7% 97300 0:28.57 0
523c400 6% 102056 0:32.84 0
9b96118 6% 120580 0:36.40 0
eead0b1 9% 119884 0:22.20 0

java_simple_multithreaded.csv

Commit CPU Memory Time ExitCode
77e1343 26% 63556 0:13.94 0
523c400 27% 65596 0:13.36 0
9b96118 24% 63564 0:14.41 0
eead0b1 17% 63604 0:22.95 0

Notes

  • The results above are generated by running against seed projects in https://github.com/getgauge/gauge-benchmark
  • These results are not persisted, but on merging to master the benchmark will be rerun.
  • These benchmark are run in Github Actions' agents, which are virtualized. Results are not to be taken as actual benchmarks.Rather, these are indicative numbers and make sense for comparison.

See Workflow log for more details.

@Elwis28
Copy link

Elwis28 commented May 4, 2024

@sriv is there a plan to finish this? It would be a very good addition to gauge.

sriv added 3 commits May 7, 2024 15:49
usage: gauge list --steps
Signed-off-by: sriv <srikanth.ddit@gmail.com>
Signed-off-by: sriv <srikanth.ddit@gmail.com>
Signed-off-by: sriv <srikanth.ddit@gmail.com>
@zabil
Copy link
Member

zabil commented May 7, 2024

Tested this as follows and all is good

⋊> gauge init js                                                                                                                                                                                                                            
Successfully initialized the project. Run specifications with "npm test" in project root.
⋊> gauge list --steps                                                                                                                                                                        16:26:50
[Steps]
Add task <item>
Add tasks <table>
Clear all tasks
Complete tasks <table>
Must display <message>
Must have <table>
Must not have <table>
Open todo application
View <type> tasks

@zabil zabil merged commit 684d870 into master May 7, 2024
29 checks passed
@zabil zabil deleted the 2432_list_steps branch May 7, 2024 15:59
@chadlwilson
Copy link
Contributor

Sigh, PyPi CLI release broken somehow again :-( Might be one of the setuptools bumps - seems to have started creating getgauge_cli instead of getgauge-cli.

BAD https://github.com/getgauge/gauge/actions/runs/8988550261/job/24689918571
last GOOD https://github.com/getgauge/gauge/actions/runs/8594066411/job/23546632610

Does anyone use that Python-installed CLI I wonder? :-/

@chadlwilson
Copy link
Contributor

chadlwilson commented May 7, 2024

Filed at #2536 for now. (ignore: rubber ducked my way to fixing it, should be OK for next release - probably no rush)

@zabil
Copy link
Member

zabil commented May 8, 2024

Does anyone use that Python-installed CLI I wonder? :-/

Not sure if we can fully trust this, but it seems like it's being downloaded a lot. From https://pypistats.org/packages/getgauge

@chadlwilson
Copy link
Contributor

Not sure if the stats can be trusted either but the package in question here (the CLI installer) is https://pypistats.org/packages/getgauge-cli rather than the other one (the python language support)

@zabil
Copy link
Member

zabil commented May 8, 2024

Ah yes you are right. So it's something around like

Downloads last day: 1
Downloads last week: 64
Downloads last month: 213

I am not sure how to interpret it. But it looks like there is decent usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Get list of steps via gauge list
4 participants