Files
simple-aircraft-manager-rails/test/integration/setup_test.rb
T
rickyandClaude Opus 5.5 d8cd462194 Configurable roles: Owner, Mechanic, Pilot, Viewer and custom roles
What people can do on an aircraft now comes from their role there, and
administrators set what each role allows (Admin → Roles).

- Roles are installation-wide sets of permissions (31, grouped as flying,
  squawks and notes, maintenance records, imports and exports, the
  aircraft, notifications). Seeing an aircraft's records needs none.
- Built in: Owner (always every permission, so an aircraft can always be
  managed), Mechanic (shop maintenance: logbook, signing, components,
  inspections, ADs, squawks, reminders), Pilot (what pilots could do
  before) and Viewer (view only). Administrators can change all but
  Owner's, and add their own; a role can be deleted once nobody has it.
- Existing owners and pilots keep exactly what they could do.
- Admin → Users → a user lists their role on every aircraft, to change,
  remove or add. On the aircraft's Access page, anyone who manages people
  hands out roles, but only an Owner can give or take away Owner, nobody
  changes their own (except administrators), and an aircraft always
  keeps an Owner (AircraftAccess).
- Controllers declare the permission each action needs; a request that
  changes something with none declared is refused (and raises in
  development and tests), and a test walks every route to check.
- Weekly reminders and overdue alerts go to roles that get reminders;
  the DRS reminder also needs Manage ADs. The API follows the person's
  role; its owners_only error is now not_permitted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 17:43:38 -05:00

32 lines
1.2 KiB
Ruby

require "test_helper"
class SetupTest < ActionDispatch::IntegrationTest
test "first run creates admin with the code from the server log, then setup is closed" do
get root_path
assert_redirected_to new_setup_path
get new_setup_path
assert_select "input[name=setup_code]"
admin = { name: "Jane", email_address: "a@b.com", password: "test-password-123", password_confirmation: "test-password-123" }
post setup_path, params: { user: admin, setup_code: "AAAA-AAAA" }
assert_response :unprocessable_entity
assert_not User.exists?
post setup_path, params: { user: admin, setup_code: SetupCode.current.downcase.delete("-") } # forgiving about case and the dash
assert_redirected_to root_path
assert_not SetupCode.file.exist?, "the code is used up"
assert User.last.admin?
get new_setup_path
assert_redirected_to root_path
end
test "create aircraft makes creator the owner" do
user = create_user
sign_in user
post aircraft_index_path, params: { aircraft: { tail_number: "N1", tach_time: 50 } }
a = Aircraft.find_by!(tail_number: "N1")
assert_redirected_to aircraft_path(a)
assert_equal "owner", user.role_for(a).key
end
end