capybara | bar manager for lemonbar

In ruby 2.6.1, rails 6.0 I am trying to get Capybara to start a test server and have the option to show or not the cases on chrome using capybara 3.35.3 and cuprite 0.13, by setting a headless option on or off.

My findings and issues:

Ideally Not define Capybara.server_host or Capybara.server_port and instead use Capybara.always_include_port = true which according to Capybara's documentation, is meant to always send or rather append the port to the server host address for whenever visit is used in a test case, the url in the browser would be http://127.0.0.1:xxxx/. The problem with this approach is that Capybara.always_include_port is not doing that, instead after the server is run, the browser goes to http://127.0.0.1/

If I set Capybara.server_port, the browser still ends up with no port upon bundle exec rspec, regardless to the state of Capybara.always_include_port.

for reference, the reason I use CAPYBARA_APP_HOST with host! before each case and not use a general Capybara.app_host is because Rails automatically changes the value of the latter to 127.0.0.1, so this is more of a work around acquired from evilmartians.

The commented lines of code are to showcase my points mentioned.

worth noting that the only way currently the environment would work is if I set Capybara.run_server = false , and uncomment the server_host, server_port, CAPYBARA_APP_HOST and host! lines, and start a seperate rails server using rails s then run the specs, which is less than ideal.

Any pointers? Thank you

my rails_helper.rb:

I am trying to setup our Rails project to use rspec. But I am getting 'No examples found' when I run rspec. How can I get rspec to run the example(s)?

I am just using the command rspec with any options or settings.

Rails: 6.0.3.4 Ruby: 2.7.2

My spec file is in the spec/requests folder and has the following content

Im running ruby version 2.6.1 with docker. Rake gem is version 13.0.1.
Whenever I tried docker-compose up, it always fails and throws this error everytime:
This error did not exist before.

I am more of a Java programmer and still somewhat new to development (2 years or so, can write Java code & web apps just fine) however the company I work for has 4 Rails applications and was asked to get this application working called CtrlPanel. I have been having to learn Ruby on Rails in order to help get this issue with this app fixed and get it working.

I have been working on this problem for over a week all day long every day and nothing I do is fixing it.

I fixed everything to the point the app comes up, web server runs serves the pages but all views are white screens as long as this application.html.haml file is present. I re-wrote the file with very basic bootstrap and it sort of works but nothing looks right. The problem seems to stem from 1 single like that simply says: = javascript_include_tag "application"

I have been all over the internet and have tried every single fix from changing coffee-script-source to v1.8.0 as I read Windows has an issue with newer rails and that file, I have tried every variation of changing it from application to default, and every type of ending you can think of no matter what I do it gives me this error message which I can not seem to find.

I am not even sure WHAT that line does, I assume it has to do with the new Google Maps API and I verified the key is valid and it was working before.

This is the error is it giving it says the line with "= javascript_include_tag" "application" giving error ExecJS::RuntimeError at / SyntaxError: [stdin]:1:1: unexpected //=

I am running a PC on Windows 10 20H2 x64 UEFI ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x64-mingw32] Rails 6.1.3

(I did also install Ubuntu on another machine and it gives the exact same error, also gives the same error on another Windows machine)

The app is working IF I delete the "application.html.haml" file and put in a skeleton basic version all of the other views start working but of course none of them look right no menus no bootstrap no nothing.
Here is the application.html.haml file.

Most stuff I can find related is about testing that the background job is scheduled like this question.

However, I need to write a feature test that actually waits for the execution of the background job, so let's say:

I am trying to write a feature spec using RSpec and Capybara which changes between two types of session_stores: cookie_store and active_record_store, and expects the user to remain logged in even though we switched from active_record_store to cookie_store. Basically for some reasons, I am switching from active_record_store to cookie_store and want to see if the session remains stored regardless of change in configuration.

This is my session_store.rb file:

I know other people have asked about this before, but I cannot find similar case to this issue.

I have two simple tests:

I have tried a couple of ways like using browser.manage.delete_cookie and also setting cookie to empty by doing something like this : page.driver.browser.manage.set_cookie("#{'cookie_name'}:") but none of them helped.

This is my Step Defn file

I am using Rails 6.1.3 with Ruby 2.7.2 for a mostly static pages app. The app has a registration form that a student must complete and download as a PDF file to print, persistence is not required at this point. It was working fine with Dhalang (Google's puppeteer wrap) gem, then I did a Javascript routine for a different part of the app and it stopped to work. The process should be: A view has a button link_to the route "new_student_url" set up to the "students_controller#new" action which should get the views/students/new to render the _form, At this point I have the button pointing and recognizing the route but when I click on it it just ignores the event; Oddly enough, if I right click the button to 'open link in a new tab', it works... =/ I have read several other cases and found that most of them are caused by a Turbolinks issue, so I did review my Turbolinks setup with Webpack and the app/javascript/packs/application.js seems to be ok, please help.

This is the link button: