-
Notifications
You must be signed in to change notification settings - Fork 5
Configuration
There are a number of locations within the project which are used to configure the project. The main configuration file is the "App.config" file within the main project folder, "gpconnect-provider-testing\GPConnect.Provider.AcceptanceTests".
In this configuration file you can configure the test suite to talk to a specific fhir endpoint, it can also be configured to use a web proxy and to pass requests through the spine sercurity proxy.
In addition to the "gpconnect-provider-testing" project you will also need to download a copy of the "gpconnect-fhir" project from the same github directory. The location of the "gpconnect-fhir" project needs to be included in the "App.config" file for the "fhirDirectory" variable. This variable is used to validate fhir resources.
Within the config file there are a number of values which need to be configured. The main ones are the "fhirServer" parameters where the provider endpoint url and port needs to be setup. The "spineProxy" elements which need configuring for the SSP being used. The certificate configuration needs updating with the thumbprints of the certificates you install in your windows certificate store which you have to talk to the SSP.
<add key="useTLS" value="true" />
<add key="fhirServerUrl" value="gpconnect-uat.answerappcloud.com" />
<add key="fhirServerPort" value="443" />
<add key="fhirServerFhirBase" value="/fhir" />
<add key="spineProxyUrl" value="" />
<add key="spineProxyPort" value="" />
<add key="clientCertThumbPrint" value="c3 1b 74 39 4b a1 60 c5 62 f1 dc 68 ee 3e 5a 3c 85 0b 32 61" />
<add key="clientInvalidCertThumbPrint" value="ea 57 be 3c 6c da 33 e6 d8 75 88 99 44 ee 61 28 4e 39 d9 1d" />
<add key="clientExpiredCertThumbPrint" value="ea 57 be 3c 6c da 33 e6 d8 75 88 99 44 ee 61 28 4e 39 d9 1e" />
On windows you will need to add the appropriate SSL certificates to the the users certificate store, usually using the "mmc" the "Microsoft Management Console".
For testing there are a some self signed certificates which are used for the GP Connect demonstrator, the certificates are included in the test suite project. There is a zip file called "TestSuiteCerts" are the root of the project which contains all the required test certificates for running the test suite. The server certificate, valid and invalid client certificates.
If you are running in the DEV or INT environment you will need to add the environment specific certificates to your windows certificate store and then within the "App.config" file mentioned above you will need to change the certificate thumbprints to match the installed environment specific certificates.
If you wish to run without SSL so that you can check messages when testing you can turn off "useTLS" for the server endpoint within the "App.config" file.
Test Suit Setup & Configuration
Tests / Scenarios
- Spine Integration and Cross Organisation Tests
- Access Record Consumer Tests
- Access Record Consumer Tests 0.5.3
- Access Record Consumer Tests 0.7.2
- Access Record Consumer Tests 0.7.3
- Foundations Consumer Tests
- Appointments Consumer Tests
- Appointments Consumer Tests 1.2.7 Emergency Changes Only
- Appointments Consumer Tests
- Structured Record Consumer Tests
- Structured Record Consumer Tests 1.2.4
- Structured Record Consumer Tests 1.2.5
- Structured Record Consumer Tests 1.2.6
- Structured Record Consumer Tests 1.3.0
- Send Document Tests 1.3.0
- Access Record HTML view Manual Testing
- Appointments API (including Foundation) - Manual Testing
- HTML Provider Content
- FHIR GP Connect Profiles
- FHIR Base
- SSP
- JWT
- HTTP
- Security
- test
Test Data Pack
- Test Data Approach
- Base Test Data Set
- Simple Patient Records
- Rich Test Data Set
- ITK Test Harness Triggers
New Consumer SCAL Tests/Scenarios