cucumber-rails | Rails Generators for Cucumber with special support | Functional Testing library
kandi X-RAY | cucumber-rails Summary
kandi X-RAY | cucumber-rails Summary
Cucumber-Rails brings Cucumber to Rails 5.x, 6.x and 7.x.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Create a new database .
- Configure environment variables
- Embed HTML template
- creates a script script
- embed contents to source
cucumber-rails Key Features
cucumber-rails Examples and Code Snippets
Community Discussions
Trending Discussions on cucumber-rails
QUESTION
Hi i was deploying a branch on heroku and threw up this error. I also tried deploying a branch which worked perfectly, but that is also showing the same error.
local yarn verion : 1.22.17 local node version : v12.22.7 Please help !!!
Tried building without yarn.lock and package-lock same thing.
This is how it starts Heroku deployment build log through CLI
...ANSWER
Answered 2021-Dec-18 at 14:32I had a similar problem but resolved by following steps.
- Run the following command.
heroku buildpacks:add heroku/nodejs --index 1
- Update node version from
16.x
to12.16.2
in package.json.
QUESTION
FINAL EDIT: I gave up and just did a full reinstallation of WSL2 and everything. Worked great. So if you're somehow dealing with this same problem, a hard reset may be a viable option.
I have already looked at many previous Stack Overflow posts, most notably this one whose second solution is echoed across most other posts on the topic, which is to extend the internal timeout to allot more time for the browser to load pages that take more than the default 60sec.
The Cucumber tests I'm running are small (the one I'm using as a baseline for this is 4 scenarios with 16 steps) and pass virtually instantly when not using Selenium, the pages are mostly static and I just want to be able to see it run+process popups in future tests, so I don't need more load time.
These tests were all working perfectly fine a few months ago (June), but when I reopened the same repo, completely unmodified now I'm unable to run any of the tests with selenium - it doesn't even open the browser anymore when run. As such, I get the feeling it doesn't have to do with my project settings, because none of it has changed. Even so, I've uninstalled the gems and reinstalled them, updated them, all to no avail. I don't know what local system settings/environment variables could have changed during this time, as I work on the app exclusively through WSL2, which I haven't touched since the last time I opened this specific project. Any ideas on this front would be very welcome.
The only configuration I've done for Capybara is setting Capybara.javascript_driver
to either :selenium
or :selenium_headless
between testing sessions in my env.rb
file, everything else is running default. My firefox and geckodriver versions are compatible.
Versions:
- Ubuntu - 20.04.1 LTS
- Ruby - 2.5.3
- Firefox - 92.0
- Geckodriver - 0.29.1
- xfce4 - 4.14 (ran
apt list -a xfce4
, asxfce4-about
gave me an error:17:02:48.578: No vendor information found in "/usr/share/xfce4/vendorinfo".
Relevant (?) Gems :
- selenium-webdriver (4.0.0.rc1)
- webdriver (0.18.0)
- cucumber (7.0.0)
- cucumber-rails (2.4.0)
Please let me know if more information of any type is required, thank you.
EDIT: Relevant Github repos: last working version from a few months ago, most recent development branch as of this post
EDIT 2,4,5: Logs for one Cucumber scenario after setting geckodriver log level to trace:
...ANSWER
Answered 2021-Sep-15 at 08:03not sure what the webdriver 0.18.0 gem is? But if you can push up a repo that we can pull down and triage, I'd be happy to help.
From your original post there's also nothing reproducible. So let us know once you have a github link. I'd wager the issue is your project / pc settings
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 cucumber-rails
Make sure you have a supported ruby installed, cd into your cucumber-rails repository and:.
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