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

Catch errors during provider initialization #1282

Closed
AndreyBelym opened this issue Mar 1, 2017 · 1 comment
Closed

Catch errors during provider initialization #1282

AndreyBelym opened this issue Mar 1, 2017 · 1 comment
Labels
AREA: server 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).
Milestone
Sprint #5

Comments

@AndreyBelym
Copy link
Contributor

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

There is no error if a provider failed at initialization.

What is the expected behavior?

Testcafe should report the initialization error.
@AndreyBelym AndreyBelym added AREA: server SYSTEM: browser natives TYPE: bug The described behavior is considered as wrong (bug). labels Mar 1, 2017
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #5 milestone Mar 1, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Mar 2, 2017
@AndreyBelym
Catch provider init errors (closes DevExpress#1282)
7e41146
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Mar 2, 2017
@AndreyBelym
Catch provider init errors (closes DevExpress#1282)
d5b2fd2
@AlexanderMoskovkin AlexanderMoskovkin mentioned this issue Mar 17, 2017
Closed
@lock
Copy link

lock bot commented Mar 29, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 29, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
@AndreyBelym @kirovboris
Catch provider init errors (closes DevExpress#1282) (DevExpress#1283)
569f516
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
AREA: server 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
Sprint #5
Development

No branches or pull requests
2 participants
@AndreyBelym @AlexanderMoskovkin