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

Regression: current or parent directories can't be used for the screenshots base paths #2975

Closed
AndreyBelym opened this issue Oct 16, 2018 · 2 comments
Closed

Regression: current or parent directories can't be used for the screenshots base paths #2975

AndreyBelym opened this issue Oct 16, 2018 · 2 comments
Assignees
@AndreyBelym
Labels
AREA: server !IMPORTANT! STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: browser natives TYPE: bug The described behavior is considered as wrong (bug).

Comments

@AndreyBelym
Copy link
Contributor

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

You can't use ./ or ../ for the screenshots base path. It generates the Forbidden character in the base screenshots path error.

What is the expected behavior?

You can use ./ and ../ for the screenshots base path.

How would you reproduce the current behavior (if this is a bug)?

testcafe -s ./ chrome test.js

Specify your

  • operating system: any
  • testcafe version: 0.22.1-alpha.3
  • node.js version: any
@AndreyBelym AndreyBelym added TYPE: bug The described behavior is considered as wrong (bug). SYSTEM: browser natives AREA: server labels Oct 16, 2018
@AndreyBelym AndreyBelym added this to the Sprint #20 milestone Oct 16, 2018
@AndreyBelym AndreyBelym self-assigned this Oct 16, 2018
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Oct 16, 2018
@AndreyBelym
Workaround for location.origin; fix regressions (DevExpress#2978, Dev…
8c578f1 
…Express#2975)
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Oct 16, 2018
@AndreyBelym
Workaround for location.origin; fix regressions (DevExpress#2978, Dev…
98197de 
…Express#2975)
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Oct 22, 2018
@AndreyBelym
Workaround for location.origin; fix regressions (DevExpress#2978, Dev…
5fe9b17 
…Express#2975)
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Oct 22, 2018
@AndreyBelym
Workaround for location.origin; fix regressions (DevExpress#2978, Dev…
ff6d299 
…Express#2975)
VasilyStrelyaev added a commit to VasilyStrelyaev/testcafe that referenced this issue Oct 23, 2018
@VasilyStrelyaev
Add DevExpress#2978 and DevExpress#2975
7184493
testcafe-build-bot added a commit to testcafe-build-bot/testcafe that referenced this issue Oct 23, 2018
@testcafe-build-bot
Add DevExpress#2978 and DevExpress#2975
53dd42f
testcafe-build-bot added a commit to testcafe-build-bot/testcafe that referenced this issue Oct 23, 2018
@testcafe-build-bot
Add DevExpress#2978 and DevExpress#2975
6adb470
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Oct 23, 2018
@AndreyBelym
Workaround for location.origin; fix regressions (DevExpress#2978, Dev…
877b162 
…Express#2975)
AndreyBelym added a commit that referenced this issue Oct 24, 2018
@AndreyBelym
Workaround for location.origin; fix regressions (#2978, #2975) (#3015)
fcacaa3
@miherlosev
Copy link
Collaborator

Fixed in fcacaa3

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or feature requests. For TestCafe API, usage and configuration inquiries, we recommend asking them on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@AndreyBelym AndreyBelym

Labels
AREA: server !IMPORTANT! STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: browser natives TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@miherlosev @AndreyBelym