Travel Registration App

Living Documentation Portal

Application behaviour — always in sync with the specification

96 Scenarios
5 Features
0 Open Feedback
✓ Happy Path 6 scenarios
Happy Path

Employee selects their persona and reaches the employee dashboard

📍 Starting from
the application is running
I am on the select-role page
▶ User action
I click the persona card for an employee persona
✓ Expected outcome
I am redirected to the dashboard
I see my employee dashboard with my travel requests
View technical spec
Scenario: Employee selects their persona and reaches the employee dashboard
  Given the application is running
  Given I am on the select-role page
  When  I click the persona card for an employee persona
  Then  I am redirected to the dashboard
  Then  I see my employee dashboard with my travel requests
Happy Path

Manager selects their persona and sees direct reports' requests

📍 Starting from
the application is running
I am on the select-role page
▶ User action
I click the persona card for a manager persona
✓ Expected outcome
I am redirected to the dashboard
I see requests submitted by employees on my team
View technical spec
Scenario: Manager selects their persona and sees direct reports' requests
  Given the application is running
  Given I am on the select-role page
  When  I click the persona card for a manager persona
  Then  I am redirected to the dashboard
  Then  I see requests submitted by employees on my team
Happy Path

HRIS admin selects their persona and accesses the admin panel

📍 Starting from
the application is running
I am on the select-role page
▶ User action
I click the persona card for an HRIS admin persona
✓ Expected outcome
I can navigate to "/hris"
I see all travel requests across the organisation
View technical spec
Scenario: HRIS admin selects their persona and accesses the admin panel
  Given the application is running
  Given I am on the select-role page
  When  I click the persona card for an HRIS admin persona
  Then  I can navigate to "/hris"
  Then  I see all travel requests across the organisation
Happy Path

Logged-in user logs out

📍 Starting from
the application is running
I am logged in as any persona
▶ User action
I click the logout link in the navigation
✓ Expected outcome
I am redirected to the login page
my session is cleared
I cannot access the dashboard without logging in again
View technical spec
Scenario: Logged-in user logs out
  Given the application is running
  Given I am logged in as any persona
  When  I click the logout link in the navigation
  Then  I am redirected to the login page
  Then  my session is cleared
  Then  I cannot access the dashboard without logging in again
Happy Path

Logged-in user accesses the FAQ page

📍 Starting from
the application is running
I am logged in as an employee
▶ User action
I navigate to "/faq"
✓ Expected outcome
I see the FAQ page content
I see a link to the Mingle travel guideline
I am not redirected to the login page
View technical spec
Scenario: Logged-in user accesses the FAQ page
  Given the application is running
  Given I am logged in as an employee
  When  I navigate to "/faq"
  Then  I see the FAQ page content
  Then  I see a link to the Mingle travel guideline
  Then  I am not redirected to the login page
Happy Path

Swiss employee persona has Employee ID and Cost Center

📍 Starting from
the application is running
I am on the select-role page
▶ User action
I click a Swiss employee persona (e.g. "swiss_employee_zh")
✓ Expected outcome
I am logged in as that persona
the new request form shows my Employee ID pre-filled
the new request form shows my Cost Center pre-filled
View technical spec
Scenario: Swiss employee persona has Employee ID and Cost Center
  Given the application is running
  Given I am on the select-role page
  When  I click a Swiss employee persona (e.g. "swiss_employee_zh")
  Then  I am logged in as that persona
  Then  the new request form shows my Employee ID pre-filled
  Then  the new request form shows my Cost Center pre-filled
⚠ Edge Cases 7 scenarios
Edge Case

Unauthenticated user is redirected to login when accessing dashboard

📍 Starting from
the application is running
I am not logged in
▶ User action
I navigate to "/dashboard/"
✓ Expected outcome
I am redirected to the login page
View technical spec
Scenario: Unauthenticated user is redirected to login when accessing dashboard
  Given the application is running
  Given I am not logged in
  When  I navigate to "/dashboard/"
  Then  I am redirected to the login page
Edge Case

Unauthenticated user is redirected to login when accessing a request

📍 Starting from
the application is running
I am not logged in
▶ User action
I navigate to "/request/1/"
✓ Expected outcome
I am redirected to the login page
View technical spec
Scenario: Unauthenticated user is redirected to login when accessing a request
  Given the application is running
  Given I am not logged in
  When  I navigate to "/request/1/"
  Then  I am redirected to the login page
Edge Case

Unauthenticated user is redirected to login when accessing new request form

📍 Starting from
the application is running
I am not logged in
▶ User action
I navigate to "/request/new/"
✓ Expected outcome
I am redirected to the login page
View technical spec
Scenario: Unauthenticated user is redirected to login when accessing new request form
  Given the application is running
  Given I am not logged in
  When  I navigate to "/request/new/"
  Then  I am redirected to the login page
Edge Case

Unauthenticated user is redirected to login when accessing notifications

📍 Starting from
the application is running
I am not logged in
▶ User action
I navigate to "/notifications/"
✓ Expected outcome
I am redirected to the login page
View technical spec
Scenario: Unauthenticated user is redirected to login when accessing notifications
  Given the application is running
  Given I am not logged in
  When  I navigate to "/notifications/"
  Then  I am redirected to the login page
Edge Case

Unauthenticated user is redirected to login when accessing admin panel

📍 Starting from
the application is running
I am not logged in
▶ User action
I navigate to "/hris/"
✓ Expected outcome
I am redirected to the login page
View technical spec
Scenario: Unauthenticated user is redirected to login when accessing admin panel
  Given the application is running
  Given I am not logged in
  When  I navigate to "/hris/"
  Then  I am redirected to the login page
Edge Case

Employee cannot access another employee's request

📍 Starting from
the application is running
I am logged in as employee "alice"
a request exists that belongs to employee "alice"
I am logged in as a different employee
▶ User action
I navigate to that request's detail page
✓ Expected outcome
I receive a 403 Forbidden response
View technical spec
Scenario: Employee cannot access another employee's request
  Given the application is running
  Given I am logged in as employee "alice"
  Given a request exists that belongs to employee "alice"
  Given I am logged in as a different employee
  When  I navigate to that request's detail page
  Then  I receive a 403 Forbidden response
Edge Case

Employee cannot access the edit form for another employee's request

📍 Starting from
the application is running
I am logged in as employee "alice"
a request exists that belongs to employee "alice"
I am logged in as a different employee
▶ User action
I navigate to that request's edit URL
✓ Expected outcome
I receive a 403 Forbidden response
View technical spec
Scenario: Employee cannot access the edit form for another employee's request
  Given the application is running
  Given I am logged in as employee "alice"
  Given a request exists that belongs to employee "alice"
  Given I am logged in as a different employee
  When  I navigate to that request's edit URL
  Then  I receive a 403 Forbidden response