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

config value dir, should work for file assertion #153

Closed
dylanhitt opened this issue Dec 1, 2020 · 0 comments
Closed

config value dir, should work for file assertion #153

dylanhitt opened this issue Dec 1, 2020 · 0 comments

Comments

@dylanhitt
Copy link
Member

dylanhitt commented Dec 1, 2020 •
edited
Loading

We are currently able to set dir for a suite and individual test cases. However, this does not respect the file assertion.

Execution context only changes for the command execution, when read the expected output the workdir is the directory where the execution of commander started.
@dylanhitt dylanhitt changed the title Add --context to set execution environment config value dir, should work for file assertion Dec 1, 2020
@dylanhitt dylanhitt mentioned this issue Dec 1, 2020
Closed
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

support workdir in matcher.FileMatcher{} commander-cli/commander
1 participant
@dylanhitt