Allow passing parameters to executable when parsing tests
See original GitHub issueI have a gtest executable which needs a path as an argument when executed like this: /path/to/test-executable /test/files
. Currently it doesn’t seem to be possible to give additional run arguments for the test discovery step in similar way as it is for running tests like: "gtest": {"additionalRunArguments": ["/test/files"]}
Would it be possible to enable passing the run arguments in the test discovery step also?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Parsing Parameters for a Script in an Executable File
Passing Parameters to a Script in an Executable File explains how to use the special parsing features of PowerShell Studio and PrimalScript ...
Read more >Passing parameters to exe - Stack Overflow
The way you pass parameters to an executable that will be launched from powershell does not change. You use executables and batch commands ......
Read more >Adding arguments and options to your Bash scripts - Red Hat
Bash uses a tool called positional parameters to provide a means of entering data into a Bash program when it is invoked from...
Read more >How Command Line Parameters Are Parsed - David Deley
Parameters passed to ShowParams.exe are parsed by ShowParams.exe . The parameter parsing rules are determined by the C++ compiler that compiled ShowParams.exe ......
Read more >Passing Test Parameters via Command Line | TestComplete ...
In your test project, create a parsing routine that will extract your custom parameters from the command line and send those parameters to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes I thought about passing the args through environment variables but in my case that would require changing various build scripts and CI build pipelines and it’s probably not feasible in this case.
But adding
additionalDiscoveryArguments
would fit my use case perfectly and enable me to use this great extension when developing on my local machine 😃I would imagine the best option would be to pass the additional args first before
--gtest*
arguments since likely the required arguments for the test executable would come first before optional arguments like--gtest_list_tests
happy testing with 2.8.12
ps: rate the app 😉