ResearchOps application visual walkthrough

Feature: Access the ResearchOps home page

  As a user researcher
  I want to access the ResearchOps home page
  So that I can choose the right ResearchOps journey for my work

  Background:
    Given I am a user researcher
    When I visit the ResearchOps home page

  Scenario: View the ResearchOps service identity
    Then I should see the service name "ResearchOps Demo Suite"
    And I should see the tagline "Objective orientated applied user research done well."
    And I should see the page heading "ResearchOps Demo Suite"
    And I should see introductory text that says "Use ResearchOps to structure applied user research with operations, governance and accessibility baked in."

  Scenario: Understand that the service is a prototype
    Then I should see a prototype banner
    And the banner should say "This is a ResearchOps prototype. Do not enter real participant personal data."

  Scenario: Navigate using the primary navigation
    Then I should see primary navigation links for:
      | Home |
      | Start research project |
      | Projects |
    And the "Home" navigation item should be shown as the current page

  Scenario: Start with a research project
    Then I should see guidance headed "Start by creating a research project"
    And I should see text explaining that "A project gives you somewhere to hold studies, participants, sessions, notes, evidence, insights and recommendations."
    And I should see text explaining that "Create the project first. Later parts of the service become useful once the research work has somewhere to live."
    And the primary call to action should be "Start a research project"

  Scenario: Move to project creation
    Given I can see the "Start a research project" call to action
    When I select "Start a research project"
    Then I should be taken to the start research project service

  Scenario: Understand the ResearchOps lifecycle
    Then I should see a section called "How ResearchOps supports a research project"
    And I should see text explaining that "ResearchOps follows the shape of a user research project. Start by creating a project. Then add studies, participants, sessions, notes, evidence, insights and recommendations as the work develops."
    And I should see text explaining that "This sequence is a mental model, not a set of first-visit shortcuts. It shows how the work becomes connected over time."
    And I should see text explaining that "Define the research work, service phase, team context and objectives."
    And I should see text explaining that "Plan a specific round of research within the project."
    And I should see text explaining that "Recruit and manage people taking part in the study."
    And I should see text explaining that "Schedule and run research sessions."
    And I should see text explaining that "Capture observations and structured session notes."
    And I should see text explaining that "Organise what was seen, heard or recorded."
    And I should see text explaining that "Analyse evidence into meaningful findings."
    And I should see text explaining that "Turn findings into decisions, actions and service improvements."

  Scenario: View the lifecycle sequence as a mental model
    Then I should see the lifecycle stages in this order:
      | Step | Stage | Purpose |
      | Step 1 of 8 | Project | Define the research work, service phase, team context and objectives. |
      | Step 2 of 8 | Study | Plan a specific round of research within the project. |
      | Step 3 of 8 | Participants | Recruit and manage people taking part in the study. |
      | Step 4 of 8 | Sessions | Schedule and run research sessions. |
      | Step 5 of 8 | Notes | Capture observations and structured session notes. |
      | Step 6 of 8 | Evidence | Organise what was seen, heard or recorded. |
      | Step 7 of 8 | Insights | Analyse evidence into meaningful findings. |
      | Step 8 of 8 | Recommendations | Turn findings into decisions, actions and service improvements. |
    And each stage should include a short explanation of what happens at that point

  Scenario: Avoid misleading lifecycle links
    Then lifecycle stages should be presented as orientation rather than as a menu
    And later lifecycle stages should not be presented as first-visit shortcuts
    And the page should make it clear that later work becomes useful after a project has been created

  Scenario: Review later ResearchOps tasks
    Then I should see a section called "What you can do after creating a project"
    And I should see text explaining that "These parts of ResearchOps are shown as orientation. They make more sense after a project record has been created."
    And I should see orientation cards for:
      | Task | Category | Availability |
      | Set clear research objectives | Team alignment | Available after project creation |
      | Recruit participants for user research studies | Recruitment | Available after study planning |
      | Turn research evidence into recommendations | Evidence and analysis | Available after sessions |

  Scenario: Understand the "Set clear research objectives" task
    Given I can see the "Set clear research objectives" orientation card
    Then I should see that it is "Available after project creation"
    And I should see the question "How might we overcome the impact of unclear objectives in user research?"
    And I should see supporting text that says "Use the project space to align stakeholder objectives with research, design and delivery work."
  Scenario: Understand the "Recruit participants for user research studies" task
    Given I can see the "Recruit participants for user research studies" orientation card
    Then I should see that it is "Available after study planning"
    And I should see the question "How might we ensure that participant recruitment reflects the diversity and needs of the service’s real users?"
    And I should see supporting text that says "Plan recruitment so findings are not biased, exclusionary or weakly connected to the service’s real users."
  Scenario: Understand the "Turn research evidence into recommendations" task
    Given I can see the "Turn research evidence into recommendations" orientation card
    Then I should see that it is "Available after sessions"
    And I should see the question "How might we keep evidence, insights and recommendations connected?"
    And I should see supporting text that says "Use structured notes and evidence trails to show how research findings lead to service decisions."
  Scenario: Use the lifecycle sequence on a mobile device
    Given I am viewing the home page on a mobile device
    Then the lifecycle sequence should remain readable
    And the stages should appear in the correct order
    And no content should require horizontal scrolling

  Scenario: Access the home page using a keyboard
    Given I am navigating with a keyboard
    Then I should be able to move focus through the primary navigation links
    And I should be able to move focus to "Start a research project"
    And I should be able to activate links, buttons and form controls without a mouse

  Scenario: Understand the page structure with assistive technology
    Then the page should have one clear main heading
    And the start guidance section should have a meaningful heading
    And the lifecycle should be marked up as an ordered sequence
    And each lifecycle stage should expose its name and explanation in a logical reading order
    And each orientation card should expose its title, supporting text and availability in a logical reading order

  Scenario: View footer information
    Then I should see the footer text "© 2026 Home Office Biometrics · ResearchOps v1.0.0"

Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 1 completed with project definition" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for project name, description, phase and status entered using believable discovery-stage dummy data.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 2 default state" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for second wizard step after a valid project definition has been entered on step 1.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 2 completed without AI rewrite invoked" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for stakeholders, objectives and user groups entered with realistic planning data before the AI rewrite is requested.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    And I enter "Priya Shah | Service owner | priya.shah@example.gov.uk Mark Evans | Operations lead | mark.evans@example.gov.uk Amelia Brown | Policy adviser | amelia.brown@example.gov.uk" into the "Stakeholders" field
    And I enter "Understand where users need assisted digital support before, during and after the application journey. Identify operational signals that help staff recognise accessibility, safegu…" into the "Research objectives" field
    And I enter "Applicants with low digital confidence, support workers, caseworkers, users with accessibility needs, users who need language support" into the "User groups" field
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 2 AI rewrite shown" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for objectives meet the AI assistance threshold and the objectives AI rewrite panel is shown using a deterministic mocked response.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    And I enter "Priya Shah | Service owner | priya.shah@example.gov.uk Mark Evans | Operations lead | mark.evans@example.gov.uk Amelia Brown | Policy adviser | amelia.brown@example.gov.uk" into the "Stakeholders" field
    And I enter "Understand where users need assisted digital support before, during and after the application journey. Identify operational signals that help staff recognise accessibility, safegu…" into the "Research objectives" field
    And I enter "Applicants with low digital confidence, support workers, caseworkers, users with accessibility needs, users who need language support" into the "User groups" field
    Then the "AI objectives support panel" section should be available
    And I select "Improve objectives with AI"
    Then I should see "Concise rewrite (optional):"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 3 default state" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for final wizard step after the project definition, stakeholders, objectives and user groups have been entered.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    And I enter "Priya Shah | Service owner | priya.shah@example.gov.uk Mark Evans | Operations lead | mark.evans@example.gov.uk Amelia Brown | Policy adviser | amelia.brown@example.gov.uk" into the "Stakeholders" field
    And I enter "Understand where users need assisted digital support before, during and after the application journey. Identify operational signals that help staff recognise accessibility, safegu…" into the "Research objectives" field
    And I enter "Applicants with low digital confidence, support workers, caseworkers, users with accessibility needs, users who need language support" into the "User groups" field
    And I select "Continue to lead researcher and notes"
    Then the "Lead researcher and notes step" section should be available
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 3 completed before create project" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for lead researcher, email and project notes entered on the final wizard step before project creation is submitted.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    And I enter "Priya Shah | Service owner | priya.shah@example.gov.uk Mark Evans | Operations lead | mark.evans@example.gov.uk Amelia Brown | Policy adviser | amelia.brown@example.gov.uk" into the "Stakeholders" field
    And I enter "Understand where users need assisted digital support before, during and after the application journey. Identify operational signals that help staff recognise accessibility, safegu…" into the "Research objectives" field
    And I enter "Applicants with low digital confidence, support workers, caseworkers, users with accessibility needs, users who need language support" into the "User groups" field
    And I select "Continue to lead researcher and notes"
    Then the "Lead researcher and notes step" section should be available
    And I enter "Alex Morgan" into the "Lead researcher name" field
    And I enter "alex.morgan@example.gov.uk" into the "Lead researcher email" field
    And I enter "Initial recruitment should include users with different levels of digital confidence and staff who handle assisted digital requests." into the "Project notes" field
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Review research projects

  As a user researcher
  I want to review existing research projects
  So that I can find the right project and continue the right ResearchOps task

  Background:
    Given I am a user researcher
    When I visit the projects page

  Scenario: Understand the page purpose
    Then I should see content that supports project list page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the projects page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Review a research project dashboard

  As a user researcher
  I want to review the status, evidence and next actions for a research project
  So that I can coordinate research activity across the team

  Background:
    Given I am a user researcher
    When I visit the project dashboard

  Scenario: Understand the page purpose
    Then I should see content that supports project dashboard page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the project dashboard
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Manage project outcomes

  As a user researcher
  I want to review findings, outputs and decisions for a project
  So that I can keep research outcomes traceable to evidence and recommendations

  Background:
    Given I am a user researcher
    When I visit the project outcomes page

  Scenario: Understand the page purpose
    Then I should see content that supports outcomes page for project-level findings and outputs.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the project outcomes page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Capture reflexive journal entries

  As a user researcher
  I want to capture reflexive notes during a project
  So that I can make assumptions, decisions and researcher influence visible

  Background:
    Given I am a user researcher
    When I visit the project journals page

  Scenario: Understand the page purpose
    Then I should see content that supports reflexive journal page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the project journals page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Review study readiness

  As a user researcher
  I want to review a study and its readiness controls
  So that I can prepare research activity before sessions begin

  Background:
    Given I am a user researcher
    When I visit the study overview page

  Scenario: Understand the page purpose
    Then I should see content that supports study overview and readiness controls.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the study overview page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Manage discussion guides

  As a user researcher
  I want to create, review and organise discussion guides for a study
  So that sessions are run with consistent and purposeful research prompts

  Background:
    Given I am a user researcher
    When I visit the discussion guides page

  Scenario: Understand the page purpose
    Then I should see content that supports discussion guide list and editor page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the discussion guides page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Manage study participants

  As a user researcher
  I want to review and manage participants for a study
  So that recruitment and session planning reflect the study needs

  Background:
    Given I am a user researcher
    When I visit the participants page

  Scenario: Understand the page purpose
    Then I should see content that supports participants page for a study.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the participants page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Run a research session

  As a user researcher
  I want to run a research session and capture notes
  So that session evidence is recorded consistently and safely

  Background:
    Given I am a user researcher
    When I visit the study session page

  Scenario: Understand the page purpose
    Then I should see content that supports session running and note capture page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the study session page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Configure study consent forms

  As a user researcher
  I want to configure the consent statements needed for a study
  So that participants can give informed consent before research activity proceeds

  Background:
    Given I am a user researcher
    When I visit the study consent forms page

  Scenario: Understand the page purpose
    Then I should see content that supports study-specific consent form configuration page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the study consent forms page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Record participant consent

  As a user researcher
  I want to record and review participant consent for a study
  So that research only proceeds where consent is clear, current and auditable

  Background:
    Given I am a user researcher
    When I visit the participant consent page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped participant consent recording and review page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Consent workspace loaded" state
    Given I am using the participant consent page
    Then the interface should make it clear that this state is for participant consent loaded with study context, a published consent form, participants and existing consent records.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Participant consent loaded."
    Then I should see "Assisted digital interview consent form"
    Then I should see "Ready for session"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Record participant consent

  As a user researcher
  I want to record and review participant consent for a study
  So that research only proceeds where consent is clear, current and auditable

  Background:
    Given I am a user researcher
    When I visit the participant consent page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped participant consent recording and review page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Missing study context error state" state
    Given I am using the participant consent page
    Then the interface should make it clear that this state is for participant consent loaded without project and study IDs; the page shows a blocking route-context message.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Open this page from a study"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Record participant consent

  As a user researcher
  I want to record and review participant consent for a study
  So that research only proceeds where consent is clear, current and auditable

  Background:
    Given I am a user researcher
    When I visit the participant consent page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped participant consent recording and review page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "No published consent form state" state
    Given I am using the participant consent page
    Then the interface should make it clear that this state is for the study has route context and participants, but no published consent form exists. The page routes the researcher to create consent forms before recording participant consent.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Create and publish a consent form before recording participant consent"
    Then I should see "Create consent forms"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Record participant consent

  As a user researcher
  I want to record and review participant consent for a study
  So that research only proceeds where consent is clear, current and auditable

  Background:
    Given I am a user researcher
    When I visit the participant consent page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped participant consent recording and review page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "No participants state" state
    Given I am using the participant consent page
    Then the interface should make it clear that this state is for the study has a published consent form, but no participants are available. The page routes the researcher to schedule participants before recording consent.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Add participants before recording consent"
    Then I should see "Schedule participants"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Record participant consent

  As a user researcher
  I want to record and review participant consent for a study
  So that research only proceeds where consent is clear, current and auditable

  Background:
    Given I am a user researcher
    When I visit the participant consent page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped participant consent recording and review page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Participant selected for consent review" state
    Given I am using the participant consent page
    Then the interface should make it clear that this state is for a researcher selects a participant with an existing consent record and can review required statements, optional permissions and withdrawal controls.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Participant consent loaded."
    And I select "Record consent"
    Then I should see "Review consent for Sofia Patel"
    Then I should see "Record withdrawal or do not proceed"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Search ResearchOps evidence

  As a user researcher
  I want to search across ResearchOps material
  So that I can find relevant evidence, records and project information quickly

  Background:
    Given I am a user researcher
    When I visit the search page

  Scenario: Understand the page purpose
    Then I should see content that supports search page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the search page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Capture research notes

  As a user researcher
  I want to capture and review research notes
  So that evidence can be used later for synthesis and decisions

  Background:
    Given I am a user researcher
    When I visit the notes page

  Scenario: Understand the page purpose
    Then I should see content that supports notes page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the notes page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Review consent information

  As a user researcher
  I want to review consent information
  So that I can understand what consent is needed before research activity continues

  Background:
    Given I am a user researcher
    When I visit the consent page

  Scenario: Understand the page purpose
    Then I should see content that supports consent page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the consent page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Review research sessions

  As a user researcher
  I want to review scheduled and completed research sessions
  So that I can coordinate session delivery and follow-up activity

  Background:
    Given I am a user researcher
    When I visit the sessions page

  Scenario: Understand the page purpose
    Then I should see content that supports sessions list page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the sessions page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Missing study ID error state" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for synthesis loaded without a study ID; the page shows the blocking route-context error.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Empty evidence state" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for study synthesis loaded with valid study context but no captured evidence notes. The page routes the researcher to evidence capture rather than showing synthesis controls.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Capture evidence before starting synthesis"
    Then I should see "Capture evidence in a session"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Evidence available before working clusters" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for study synthesis with realistic evidence available. The first available task is creating a working cluster grouping; evidence selection remains hidden until a cluster exists.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Create a working cluster grouping before selecting evidence."
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Working cluster grouping created" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for a researcher creates a provisional working cluster grouping before adding evidence. Evidence selection becomes available only after the cluster exists.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Confidence before the form starts" into the "Working cluster label" field
    And I enter "Evidence about how users judge whether they are ready to begin the service." into the "Working cluster description" field
    And I select "Create working cluster grouping"
    Then I should see "Created working cluster grouping Confidence before the form starts."
    Then I should see "I was not sure whether I had the right documents before I started, so I nearly called the helpline instead of continuing online."
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Evidence added to working cluster grouping" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for a researcher selects two evidence notes and adds them to an existing working cluster grouping. Theme creation becomes available after evidence is grouped.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I select the "evidence item" checkbox
    And I select the "evidence item" checkbox
    And I choose "cluster-confidence-start" from the "Target working cluster grouping" field
    And I select "Add selected evidence to the working cluster grouping"
    Then I should see "Added 2 evidence items to Confidence before the form starts."
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Theme creation hidden before evidence is grouped" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for theme creation remains hidden until at least one working cluster grouping contains source evidence.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then the "working cluster grouping" section should be available
    Then I should see "Add evidence to a working cluster grouping before creating a theme."
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse

Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Theme created with evidence traceability" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for a theme is created from a populated cluster and the source evidence IDs remain inspectable.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I choose "cluster-confidence-start" from the "Working cluster grouping for the theme" field
    And I enter "Digital confidence is shaped before the form starts" into the "Theme label" field
    And I enter "Users decide whether to continue based on evidence expectations, support routes and confidence before they begin entering details." into the "Theme description" field
    And I select "Create theme"
    Then I should see "Created theme Digital confidence is shaped before the form starts."
    And I select "theme traceability details"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse