-
Notifications
You must be signed in to change notification settings - Fork 673
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
Add the capability to get browser console messages #1738
Labels
STATE: Auto-locked
An issue has been automatically locked by the Lock bot.
TYPE: enhancement
The accepted proposal for future implementation.
Milestone
Comments
AlexanderMoskovkin
changed the title
Add ability to get browser console messages
Add the capability to get browser console messages
Aug 29, 2017
One usecase for it would be to make tests fail on React PropTypes errors (React uses |
dimaip
added a commit
to dimaip/neos-ui
that referenced
this issue
Aug 30, 2017
Can be removed when this is implemented: DevExpress/testcafe#1738
AlexanderMoskovkin
added
TYPE: enhancement
The accepted proposal for future implementation.
and removed
TYPE: proposal
labels
Sep 12, 2017
AlexanderMoskovkin
added a commit
to AlexanderMoskovkin/testcafe
that referenced
this issue
Sep 26, 2017
AlexanderMoskovkin
added a commit
to AlexanderMoskovkin/testcafe
that referenced
this issue
Sep 26, 2017
AlexanderMoskovkin
added a commit
to AlexanderMoskovkin/testcafe
that referenced
this issue
Oct 4, 2017
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
bot
added
the
STATE: Auto-locked
An issue has been automatically locked by the Lock bot.
label
Mar 28, 2019
kirovboris
pushed a commit
to kirovboris/testcafe-phoenix
that referenced
this issue
Dec 18, 2019
…#1738) (DevExpress#1818) * Add the capability to get browser console messages (closes DevExpress#1738) * Rename to `getBrowserConsoleMessages` * Address Helen's remarks * Fix the test for node 4 * Store messages on the server * Integrating with Roles. Refactoring. * Fix tests.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
STATE: Auto-locked
An issue has been automatically locked by the Lock bot.
TYPE: enhancement
The accepted proposal for future implementation.
Are you requesting a feature or reporting a bug?
feature suggestion
What is the expected behavior?
It allows to check messages that your application outputs via
console.log()
,console.warn()
,console.error()
,console.info()
.One of possible use cases is described in the Catch JS errors and console output discussion. React notifies about a
PropTypes
error viaconsole.error
but doesn't call something likethrow new Error()
.Proposed API:
Feel free to vote for the feature if you consider it useful and please let us know about your use case for it.
The text was updated successfully, but these errors were encountered: