Files
grecia/spec/system/admin/valuators_spec.rb
Javi Martín 5311daadfe Use a button for non-GET table actions
Links acting like buttons have a few disadvantages.

First, screen readers will announce them as "links". Screen reader users
usually associate links with "things that get you somewhere" and buttons
with "things that perform an action". So when something like "Delete,
link" is announced, they'll probably think this is a link which will
take them to another page where they can delete a record.

Furthermore, the URL of the link for the "destroy" action might be the
same as the URL for the "show" action (only one is accessed with a
DELETE request and the other one with a GET request). That means screen
readers could announce the link like "Delete, visited link", which is
very confusing.

They also won't work when opening links in a new tab, since opening
links in a new tab always results in a GET request to the URL the link
points to.

Finally, submit buttons work without JavaScript enabled, so they'll work
even if the JavaScript in the page hasn't loaded (for whatever reason).

For all these reasons (and probably many more), using a button to send
forms is IMHO superior to using links.

There's one disadvantage, though. Using `button_to` we create a <form>
tag, which means we'll generate invalid HTML if the table is inside
another form. If we run into this issue, we need to use `button_tag`
with a `form` attribute and then generate a form somewhere else inside
the HTML (with `content_for`).

Note we're using `button_to` with a block so it generates a <button>
tag. Using it in a different way the text would result in an <input />
tag, and input elements can't have pseudocontent added via CSS.

The following code could be a starting point to use the `button_tag`
with a `form` attribute. One advantage of this approach is screen
readers wouldn't announce "leaving form" while navigating through these
buttons. However, it doesn't work in Internet Explorer.

```
ERB:

<% content_for(:hidden_content, form_tag(path, form_options) {}) %>
<%= button_tag text, button_options %>

Ruby:

def form_id
  path.gsub("/", "_")
end

def form_options
  { id: form_id, method: options[:method] }
end

def button_options
  html_options.except(:method).merge(form: form_id)
end

Layout:

<%= content_for :hidden_content %> # Right before the `</body>`
```
2021-09-20 20:27:37 +02:00

115 lines
3.4 KiB
Ruby

require "rails_helper"
describe "Admin valuators", :admin do
let!(:user) { create(:user, username: "Jose Luis Balbin") }
let!(:valuator) { create(:valuator, description: "Very reliable") }
scenario "Show" do
visit admin_valuator_path(valuator)
expect(page).to have_content valuator.name
expect(page).to have_content "Very reliable"
expect(page).to have_content valuator.email
expect(page).to have_content "Can comment, Can edit dossier"
end
scenario "Index" do
visit admin_valuators_path
expect(page).to have_content(valuator.name)
expect(page).to have_content(valuator.email)
expect(page).not_to have_content(user.name)
end
scenario "Create" do
visit admin_valuators_path
fill_in "search", with: user.email
click_button "Search"
expect(page).to have_content(user.name)
click_button "Add to valuators"
within("#valuators") do
expect(page).to have_content(user.name)
end
end
scenario "Edit" do
visit edit_admin_valuator_path(valuator)
expect(page).to have_field("Can create comments", checked: true)
expect(page).to have_field("Can edit dossiers", checked: true)
fill_in "valuator_description", with: "Valuator for health"
uncheck "Can edit dossiers"
click_button "Update Valuator"
expect(page).to have_content "Valuator updated successfully"
expect(page).to have_content valuator.email
expect(page).to have_content "Valuator for health"
expect(page).to have_content "Can comment"
expect(page).not_to have_content "Can edit dossier"
end
scenario "Destroy" do
visit admin_valuators_path
accept_confirm { click_button "Delete" }
within("#valuators") do
expect(page).not_to have_content(valuator.name)
end
end
context "Search" do
let!(:user1) { create(:user, username: "David Foster Wallace", email: "david@wallace.com") }
let!(:user2) { create(:user, username: "Steven Erikson", email: "steven@erikson.com") }
let!(:valuator1) { create(:valuator, user: user1) }
let!(:valuator2) { create(:valuator, user: user2) }
before do
visit admin_valuators_path
end
scenario "returns no results if search term is empty" do
expect(page).to have_content(valuator1.name)
expect(page).to have_content(valuator2.name)
fill_in "search", with: " "
click_button "Search"
expect(page).to have_content("Valuators: User search")
expect(page).to have_content("No results found")
expect(page).not_to have_content(valuator1.name)
expect(page).not_to have_content(valuator2.name)
end
scenario "search by name" do
expect(page).to have_content(valuator1.name)
expect(page).to have_content(valuator2.name)
fill_in "search", with: "Foster"
click_button "Search"
expect(page).to have_content("Valuators: User search")
expect(page).to have_field "search", with: "Foster"
expect(page).to have_content(valuator1.name)
expect(page).not_to have_content(valuator2.name)
end
scenario "search by email" do
expect(page).to have_content(valuator1.email)
expect(page).to have_content(valuator2.email)
fill_in "search", with: valuator2.email
click_button "Search"
expect(page).to have_content("Valuators: User search")
expect(page).to have_field "search", with: valuator2.email
expect(page).to have_content(valuator2.email)
expect(page).not_to have_content(valuator1.email)
end
end
end