chore: PRs to support Client 2 (#1166)

* fix(deps): update maven all non-major dependencies * feat(fe:FSADT1-1503): Adjust button and message for the "Need help?" side menu item (#1164) * feat(fe:FSADT1-1445): Change "Logout" icon in "My profile" panel (#1165) * feat(fe:FSADT1-1445): Change "Logout" icon in "My profile" panel * Removed unused import * feat(fe:FSADT1-1502): Adjust logout behavior (#1167) * fix(fe: FSADT1-1427): Autocomplete emitting value twice (#1170) * fix: prevent from re-emitting with value undefined * test: update tests * feat(fe:FSADT1-1510): Load Legal Types description from data convertor (#1169) * fix(deps): update dependency date-fns to v4 * fix(fe: FSADT1-1495): Add notification to all BC Registries cards in step 1 (#1171) fix: show the Read-only notification always * chore: update support/client2 with main (#1175) * fix(deps): update maven all non-major dependencies * fix(deps): update dependency date-fns to v4 (#1173) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * fix(fe: FSADT1-1511): Clear business information when a new Client name gets selected (#1176) fix: clear business information when a new client name gets selected * feat(FSADT1-779): adding cypress scenarios (#1139) * feat: adding some cypress code * feat: adding gherking issue template * feat: updated commands and feature files * feat: adding core cypress instructions for user flow * chore: testing env var * chore: testing artifact grab * chore: ci update * chore: debugging * chore: reducing verbosity * chore: removing test data * feat: adding initial sample for creation * docs: updated documentation * feat: clean before run This will make the database remove the test data beforehand. This can affect the manual test too, but is the price for now * fix: fixing clean script * chore: changing strategy for cleanup - Changed strategy for cleanup. First remove everything from the PR database before recreating it. This is required due to tue uncertainty of the data that will be created through cypress and the previous, manual data inserted as well * chore: testing a few new steps * chore: pre-tools cleanup * fix: fixing automation test * fix: fixing staff on automation * chore: changing wait time * chore: adding an address * chore: trying to make a miracle * chore: scale down * chore: changing config * ci: lets do it * chore: some tests * ci: scale down post work and scale up * chore: adding tags to make it easier to find component * chore: updating name part * chore: updating a little bit * chore: adding bceid and bcsc button text * feat: updated login hooks * feat: add tag identifier for internal and external user * feat: added initial bceid * chore: adding contact identification for old screens * chore: changed limits for submission * chore: adding identification to notification * fix: fixing submit instruction * chore: splitting up the instructions * fix: fixed bceid * docs: updated readme for cypress * chore: updating notification identification * fix: fixing automation * feat(FSADT1-779): updating gherkin issue template * feat: added action to generate feature files * docs: updated readme * chore: reverting a change on accordion item title * fix: fixing wrapper * chore: adding decorator config * fix: fixing data-text location * chore: changing data-text location * fix: changing data-text location * fix: fixing contact selector * chore: removing extra data-text * chore: fixing subgroup search * feat(FSADT1-1515): Display informative message when Legal Types are not supported (#1178) * feat(FSADT1-1515): Display informative message when Legal Types are not supported * feat(FSADT1-1515): Display informative message when Legal Types are not supported * Made code reviews --------- Co-authored-by: Paulo Gomes da Cruz Junior <[email protected]> * feat(FSADT1-779): adding cypress scenarios (#1139) (#1179) * feat(FSADT1-779): adding cypress scenarios (#1139) * feat(FSADT1-779): adding cypress scenarios (#1139) * chore: merge main into client2 to solve conflicts (#1181) * fix(deps): update maven all non-major dependencies * fix(deps): update dependency date-fns to v4 (#1173) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * fix(FSADT1-1514): fixed doing business as processing (#1177) - added to external users the DBA field filled - fixed the DBA field on the processor * fix(deps): update dependency org.springframework.boot:spring-boot-starter-parent to v3.3.4 --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Paulo Gomes da Cruz Junior <[email protected]> * ci(deps): updating deployer and workflows (#1185) * fix(fe: FSADT1-1488): revalidate the date value properly (#1188) fix: validate date of birth on revalidate event * chore: upgrade vue (#1193) chore: upgraded vue * chore: update support/client2 with main (#1192) * fix(deps): update maven all non-major dependencies * fix(deps): update dependency date-fns to v4 (#1173) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * fix(FSADT1-1514): fixed doing business as processing (#1177) - added to external users the DBA field filled - fixed the DBA field on the processor * fix(deps): update dependency org.springframework.boot:spring-boot-starter-parent to v3.3.4 * chore(deps): update maven all non-major dependencies --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Paulo Gomes da Cruz Junior <[email protected]> Co-authored-by: Maria Martinez <[email protected]> * fix(fe:FSADT1-1508): reset validation when the selected Client name changes (#1191) * fix: reset validation when the selected Client name changes * fix: fix cypress commands declaration --------- Co-authored-by: Maria Martinez <[email protected]> * fix(fe: FSADT1-1421): fix date validation for pasted/autocompleted values (#1187) * fix: fix date validation for pasted/autocompleted values * test: remove .only --------- Co-authored-by: Maria Martinez <[email protected]> * chore: upgrade types node (#1194) chore: upgraded types/node * fix(fe): stop date validation when part of it has an error (#1197) fix: stop validation when any parts have errors * chore: upgraded sass (#1195) * chore: upgrade carbon pictograms (#1196) chore: updgraded carbon pictograms Co-authored-by: Fernando Terra <[email protected]> * chore: upgrade carbon styles (#1198) * chore: upgraded carbon styles * Delete frontend/src/pages/SearchPage.vue * chore: upgrade vue and cypress coverage (#1200) * fix(FSADT1-1514): fixed doing business as processing (#1177) - added to external users the DBA field filled - fixed the DBA field on the processor * chore(deps): update maven all non-major dependencies --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Fernando Terra <[email protected]> Co-authored-by: Paulo Gomes da Cruz Junior <[email protected]>
bcgov · Oct 1, 2024 · 8b35633 · 8b35633
1 parent e9e9cbf
commit 8b35633
Show file tree

Hide file tree

Showing 72 changed files with 2,518 additions and 575 deletions.
diff --git a/.github/ISSUE_TEMPLATE/cypress.yml b/.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
diff --git a/.github/workflows/analysis.yml b/.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!"
diff --git a/.github/workflows/issue-gherkin.yml b/.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 }}