v0.2.1 release

.github/workflows/dotnet.yml

@@ -143,3 +143,58 @@ jobs:
       run: |
         docker-compose -f './mock-data-recipient/Source/docker-compose.UnitTests.yml' down
 
+    # Archive unit test results
+    - name: Archive unit test results
+      uses: actions/upload-artifact@v2
+      if: always()
+      with:
+        name: unit-test-results
+        path: ${{ github.workspace }}/mock-data-recipient/Source/_temp/mock-data-recipient-unit-tests/testresults
+
+    # Archive integration test results
+    - name: Archive integration test results
+      uses: actions/upload-artifact@v2
+      if: always()
+      with:
+        name: integration-test-results
+        path: ${{ github.workspace }}/mock-data-recipient/Source/_temp/mock-data-recipient-integration-tests/testresults
+
+    # Archive e2e test results
+    - name: Archive e2e test results
+      uses: actions/upload-artifact@v2
+      if: always()
+      with:
+        name: e2e-test-results
+        path: ${{ github.workspace }}/mock-data-recipient/Source/_temp/mock-data-recipient-e2e-tests/testresults
+
+    # Archive mock data recipient logs
+    - name: Archive mock data recipient logs
+      uses: actions/upload-artifact@v2
+      if: always()
+      with:
+        name: integration-test-artifacts
+        path: ${{ github.workspace }}/mock-data-recipient/Source/_temp/mock-data-recipient/tmp
+
+    # Archive mock data holder logs
+    - name: Archive mock data holder logs
+      uses: actions/upload-artifact@v2
+      if: always()
+      with:
+        name: integration-test-artifacts
+        path: ${{ github.workspace }}/mock-data-recipient/Source/_temp/mock-data-holder/tmp
+
+    # Archive mock data holder energy logs
+    - name: Archive mock data holder energy logs
+      uses: actions/upload-artifact@v2
+      if: always()
+      with:
+        name: integration-test-artifacts
+        path: ${{ github.workspace }}/mock-data-recipient/Source/_temp/mock-data-holder-energy/tmp
+
+    # Archive mock register logs
+    - name: Archive mock register logs
+      uses: actions/upload-artifact@v2
+      if: always()
+      with:
+        name: integration-test-artifacts
+        path: ${{ github.workspace }}/mock-data-recipient/Source/_temp/mock-register/tmp

.github/workflows/test-report.yml

@@ -34,3 +34,17 @@ jobs:
         name: Integration Tests
         path: '*.trx'
         reporter: dotnet-trx
+
+  e2e-test-report:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+
+    - name: Publish e2e Test Report
+      uses: dorny/test-reporter@v1
+      with:
+        artifact: e2e-test-results
+        name: e2e Tests
+        path: '*.trx'
+        reporter: dotnet-trx

CHANGELOG.md

@@ -6,6 +6,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.1] - 2022-06-09
+### Changed
+- Build and Test action to archive test results. End to end tests now included in test report.
+
 ## [0.2.0] - 2022-05-25
 ### Added
 - PKCE support added to "Consent and Authorisations" and "PAR" in preparation for FAPI 1.0.
@@ -40,4 +44,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.0] - 2021-10-01
 
 ### Added
-- First release of the Mock Data Recipient.
+- First release of the Mock Data Recipient.

CertificateManagement/README.md

@@ -2,7 +2,7 @@
 
 Certificates play an important part in the CDR ecosystem to establish trust between participants and protect communications.  **DigiCert** is the Certificate Authority (CA) for the CDR and the ACCC is responsible for provisioning DigiCert certificates to participants during the on-boarding process.
 
-For more information, consult the [Certificate Management](https://cdr-register.github.io/register/#certificate-management) section of the Register Design.
+For more information, consult the [Certificate Management](https://consumerdatastandardsaustralia.github.io/standards/#certificate-management) section of the Consumer Data Standards.
 
 The Mock Data Recipient will mimic the behaviour of a data recipient in the CDR ecosystem and therefore will use certificates in its interactions.  However, the use of DigiCert for this purpose is not feasible or scalable so an alternative approach is adopted.