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

bug: venom doesn't display full path name of test suite #254

Closed
nqb opened this issue May 12, 2020 · 3 comments · Fixed by #273
Closed

bug: venom doesn't display full path name of test suite #254

nqb opened this issue May 12, 2020 · 3 comments · Fixed by #273
Assignees

Comments

@nqb
Copy link
Contributor

nqb commented May 12, 2020

If you use an absolute path to a file which is long, time execution overrides path name.

Steps to reproduce

  1. Create a test suite with a loooong absolute path
$ mkdir -p /tmp/path/to/a/long/filename/
$ cat >> /tmp/path/to/a/long/filename/test_suite_name.yml << EOF
> name: Title of TestSuite
> testcases:
> - name: Check if exit code != 1 and echo command response in less than 1s
>   steps:
>   - script: echo 'foo'
>     assertions:
>     - result.code ShouldEqual 0
>     - result.timeseconds ShouldBeLessThan 1
> EOF
  1. Run tests
$ venom run /tmp/path/to/a/long/filename/test_suite_name.yml
SUCCESS /tmp/path/to/a/long/filename/test_suite_name.ym13.081607ms
[..]

Actual results

We can see that last character of filename (l) is not displayed

Expected results

Display full path name.

@nqb
Copy link
Contributor Author

nqb commented Oct 7, 2020

Hello @yesnault,

Any chance this one can be fixed before release of 0.28 ?

@yesnault yesnault self-assigned this Oct 7, 2020
yesnault added a commit that referenced this issue Oct 7, 2020
close #254

Signed-off-by: Yvonnick Esnault <yvonnick.esnault@corp.ovh.com>
fsamin pushed a commit that referenced this issue Oct 7, 2020
close #254

Signed-off-by: Yvonnick Esnault <yvonnick.esnault@corp.ovh.com>
@yesnault
Copy link
Member

yesnault commented Oct 7, 2020

Hello @yesnault,

Any chance this one can be fixed before release of 0.28 ?

yes, there is a chance :)

@nqb
Copy link
Contributor Author

nqb commented Oct 7, 2020

Thanks !

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

Successfully merging a pull request may close this issue.

2 participants