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

Cucumber step to run literal script broken on Windows #521

Open
UltimateGeek opened this issue Dec 7, 2017 · 7 comments
Open

Cucumber step to run literal script broken on Windows #521

UltimateGeek opened this issue Dec 7, 2017 · 7 comments
Milestone

Comments

@UltimateGeek
Copy link

Summary

On Windows, Aruba fails to run the temporary script it creates from:

When I run the following commands:
  ```
  echo foo
  ```

Expected Behavior

Then the output should contain "foo"

Current Behavior

The step fails with output:

Command "myscript" not found in PATH-variable "C:/...

Your Environment

  • Version used: 1.0.0.pre.alpha.2
  • Operating System and version: Win7
@stale
Copy link

stale bot commented Feb 5, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

@stale stale bot added the stale These issues were closed by stalebot and need to be reviewed to see if they're still relevant. label Feb 5, 2018
@UltimateGeek
Copy link
Author

The problem is cmd.exe on Windows needs to be given a full or relative path to the script created.

@stale stale bot removed the stale These issues were closed by stalebot and need to be reviewed to see if they're still relevant. label Feb 6, 2018
@mvz
Copy link
Contributor

mvz commented Mar 4, 2018

Windows support is rather experimental I'm afraid. I'll see what I can do. Which version of Aruba are you using?

@UltimateGeek
Copy link
Author

Version used: 1.0.0.pre.alpha.2

Thank you @mvz

@mvz mvz added the bug label Mar 5, 2018
@MartyGentillon
Copy link

I see the same on 0.14.5.

@stale
Copy link

stale bot commented Jun 11, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

@stale stale bot added the stale These issues were closed by stalebot and need to be reviewed to see if they're still relevant. label Jun 11, 2018
@stale stale bot removed the stale These issues were closed by stalebot and need to be reviewed to see if they're still relevant. label Jun 12, 2018
@mvz mvz added the windows label Mar 13, 2019
@mvz mvz added this to the 1.1.0 milestone Jan 2, 2020
@mvz mvz modified the milestones: 1.1.0, 1.2.0 Aug 21, 2020
@mvz mvz modified the milestones: 1.1.0, 2.0.0 Jun 20, 2021
@mvz mvz changed the title cucumber step to run pystring script broken on Windows Cucumber step to run literal script broken on Windows Jul 26, 2021
@mvz
Copy link
Contributor

mvz commented Jul 26, 2021

I think the generated script should be named myscript.bat on Windows.

@mvz mvz modified the milestones: 2.0.0, 2.1.0 Aug 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants