chore: PRs to support Client 2

.github/ISSUE_TEMPLATE/cypress.yml

@@ -0,0 +1,65 @@
+name: User provided automated tests
+description: Submit Gherkin scenarios to generate .feature files for our test suite.
+title: '[Test Case]: REPLACE WITH YOUR TEST CASE TITLE'
+labels: gherkin, automated test
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 📝 Gherkin Scenario Submission
+
+        Thank you for contributing! Please provide your Gherkin scenario in the format below. 
+
+        ### Gherkin/Cucumber Test Scenario
+        - ✍️ **Write or paste your Gherkin scenario in the first block**:  
+          - Ensure the scenario follows the structure of **Given**, **When**, **Then**.
+          - Ensure the scenario contains a **Feature** and **Scenario** instruction.
+          - You can have multiple **Scenarios** in a single **Feature**.
+          - Pay attention to the **indentation** and **keywords**, as misconfigured files will cause issues when executed.
+          - Pay attention to the data you're using in your scenario. Make sure it don't pose a security risk or exposes any **REAL** [personal identifiable information](https://www2.gov.bc.ca/gov/content/governments/services-for-government/information-management-technology/privacy/personal-information).
+          - If you're unsure how to format your scenario, [click here for a guide](https://github.com/bcgov/nr-forest-client/tree/main/cypress#readme).
+        - 🧩 **Additional instructions**:  
+          - Use the second block to provide any **non-default** steps or custom behavior that doesn’t fit into our predefined instructions. You can find a list of ready-made instructions in [our documentation](https://github.com/bcgov/nr-forest-client/tree/main/cypress#readme).
+
+        ### Example
+
+        ```gherkin
+        Feature: Guess the word
+
+          # The first example has two steps
+          Scenario: Maker starts a game
+            When the Maker starts a game
+            Then the Maker waits for a Breaker to join
+
+          # The second example has three steps
+          Scenario: Breaker joins a game
+            Given the Maker has started a game with the word "silky"
+            When the Breaker joins the Maker's game
+            Then the Breaker must guess a word with 5 characters
+        ```
+  - type: textarea
+    id: gherkin_scenario
+    attributes:
+      label: Test Scenario
+      description: 'Please write or paste your Gherkin scenario here.'
+      render: gherkin
+      placeholder: |        
+        Feature: [Feature Name]
+          Scenario: [Scenario Name]
+            Given [some initial context]
+            When [some event occurs]
+            Then [some outcome should occur]
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional_instructions
+    attributes:
+      label: Additional Instructions
+      description: 'Please provide any additional instructions or custom behavior that doesn’t fit into our predefined instructions.'      
+      render: shell
+      placeholder: |        
+        - [Instruction 1] - [Description]
+        - [I can choose "rock" as the word] - User can provide a custom word to guess.
+    validations:
+      required: false

.github/workflows/analysis.yml

@@ -31,6 +31,6 @@ jobs:
   results:
     name: Analysis Results
     needs: [tests-java, tests-frontend, repo-reports]
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-24.04
     steps:
       - run: echo "Workflow completed successfully!"

.github/workflows/issue-gherkin.yml

@@ -0,0 +1,49 @@
+name: Create Gherkin Feature from Issue
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  create-feature:
+    if: contains(github.event.issue.labels.*.name, 'gherkin')
+    runs-on: ubuntu-24.04
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+          fetch-depth: 0
+
+      - name: Extract feature content
+        id: feature
+        uses: bcgov-nr/[email protected]
+        with:
+          issue: ${{ github.event.issue.number }}
+          default_title: "[Test Case]: REPLACE WITH YOUR TEST CASE TITLE"
+          update_title: true
+
+      - name: Create feature file
+        run: echo "${{ steps.feature.outputs.feature }}" > cypress/cypress/e2e/upt_${{ github.event.issue.number }}.feature
+
+      - name: Commit & Push changes
+        uses: Andro999b/[email protected]
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          branch: test/upt_${{ github.event.issue.number }}
+          force: true
+          message: |
+            test(upt #${{ github.event.issue.number }}): ${{ steps.feature.outputs.title }}
+
+            Closes #${{ github.event.issue.number }}
+
+      - name: Create Pull Request
+        uses: peter-evans/create-pull-request@v5
+        with:
+          branch: test/upt_${{ github.event.issue.number }}
+          title: "test(upt #${{ github.event.issue.number }}): ${{ steps.feature.outputs.title }}"
+          body: |
+            ${{ github.event.issue.body }}
+
+            Closes #${{ github.event.issue.number }}