capybara-chrome | Chrome driver for Capybara using Chrome | UI Testing library
kandi X-RAY | capybara-chrome Summary
kandi X-RAY | capybara-chrome Summary
Chrome driver for Capybara using Chrome's remote debugging protocol
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Waits for the event .
- Send a message to the server
- Loop through the list of events handlers
- Sets network socket events .
- This method is called when a selector control is selected .
- Scroll to the element .
- Return an array of modifier keys
- Setup the connection .
- Starts web browser browser server .
- Requests a node on the server .
capybara-chrome Key Features
capybara-chrome Examples and Code Snippets
Community Discussions
Trending Discussions on capybara-chrome
QUESTION
I have a Rails (5.2.3) application to which I'm trying to add a chat feature so the users can communicate with each other. I have not fully implemented the feature, as I am trying to write tests as I go (if I don't know how to write tests for what I'm trying to test, I often do it this way). So far, I have two regions of the relevant page of the application laid out in HTML for the sending and reception of chat messages, JavaScript that runs the rest of the page, JavaScript that is intended to run on page load that makes the regions for the chat feature fill out the correct space of the page, JavaScript that listens to the textarea for chats to send, and JavaScript that listens for broadcast chats. The relevant test mimics what I can do at the moment in the development version: type text in the sending </code>, hit return, and see the message in the
that holds the chats. The development logs show that the message hits the redis server and are forwarded as expected.
The chat tool test fails. If I open the console in the browser running the tests, I see neither errors nor evidence that the JavaScript on the page is executed for this test (all of the other tests, all of which are tagged @javascript execute correctly). If I add enough of a delay, I can see that both of the methods I've employed to send the enter key to the textarea appear to work (in that the cursor moves), but the expected behavior on the page (that the text is sent to the redis server for broadcast) doesn't occur.
There's no evidence in the test log that the ActionCable server fires up. I have capybara-chromedriver-logger installed, but I see no evidence of the logging I would expect.
If there is information missing from my question that you think would be helpful in answering it, please ask.
The CoffeeScript I've written for the chat elements (which executes in development, but not in the test):
...ANSWER
Answered 2020-Feb-20 at 20:03Generally one would use the async actioncable adapter when testing (not the redis adapter) and you'd need to configure actioncable to run in app (in the test environment) - https://guides.rubyonrails.org/action_cable_overview.html#in-app - in order for it to start up when Capybara starts the application.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install capybara-chrome
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
