${BROWSER} resolves to undefined in screenshot pattern #2742
Assignees
Labels
AREA: server
STATE: Auto-locked
An issue has been automatically locked by the Lock bot.
SYSTEM: reporting
TYPE: bug
The described behavior is considered as wrong (bug).
Milestone
Comments
AndreyBelym
added
TYPE: bug
|
I'm working on it. |
miherlosev
pushed a commit
to miherlosev/testcafe
that referenced
this issue
Aug 31, 2018
|
Hi @cullophid! The fix is released in |
|
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
bot
added
the
STATE: Auto-locked
kirovboris
pushed a commit
to kirovboris/testcafe-phoenix
that referenced
this issue
Dec 18, 2019
…evExpress#2742) (DevExpress#2794) * fix '${BROWSER} resolves to undefined in screenshot pattern' (close DevExpress#2742) * fix review issue
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Are you requesting a feature or reporting a bug?
bug
What is the current behavior?
when using ${BROWSER} in screenshot pattern it resolves to undefined
What is the expected behavior?
should resolve to the browser name
How would you reproduce the current behavior (if this is a bug)?
use any pattern with ${BROWSER}
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
Specify your
The text was updated successfully, but these errors were encountered: