Skip to content

Shared test cases across multiple FHIR reference implementations / validators

License

Notifications You must be signed in to change notification settings

FirelyTeam/fhir-test-cases

 
 

Repository files navigation

fhir-test-cases

CI Status (master) Release Pipeline Current Release Latest SNAPSHOT
Build Status Build Status Release Artifacts Snapshot Artifact

Contents

This repository contains:

  • r5: r5 test cases (actively maintained)
  • r4: r4 test cases (not maintained)
  • cda: test case CDA for roundtripping/validation based on FHIR definition of CDA
  • ucum: source for ucum
  • validator - test cases for the cross-version validation
  • target - maven administrative stuff

Accessing the test cases

You can access the test cases via Maven. If using Maven doesn't suit, then another option is to download the test cases directly from https://github.com/FHIR/fhir-test-cases/releases/latest/download/testcases.zip

Building this Project

This project uses Apache Maven to build. To build:

mvn install

Note: there's no java code in here. The fact that maven is used is just to make it easy to book up other maven dependencies to the test cases

Download

Maven

<dependency>
    <groupId>org.hl7.fhir.testcases</groupId>
    <artifactId>fhir-test-cases</artifactId>
    <version>(latest version)</version>
</dependency>

Gradle

compile group: 'org.hl7.fhir.testcases', name: 'fhir-test-cases', version: '(latest version)'

Releases

Releases and release notes are published to GitHub, and can also be downloaded from Maven Central.

CI/CD

This project has pipelines hosted on Azure Pipelines.

  • Pull Request Pipeline is automatically run for every Pull Request to ensure that the project can be built via maven. [Azure Pipeline] [source]
  • Master Branch Pipeline is automatically run whenever code is merged to the master branch and builds the SNAPSHOT binaries distributed to OSSRH [Azure Pipeline][source]
  • Release Branch Pipeline is run manually whenever a release is ready to be made. It builds the release binaries, distributes them to artifact repositories and sends release notifications. [Azure Pipeline][source]

A brief overview of our publishing process is here.

For more detailed instructions on cutting a release, please read the wiki

Maintenance

This project is maintained by the FHIR community to help implementations test their functionality.

About

Shared test cases across multiple FHIR reference implementations / validators

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • HTML 99.4%
  • Batchfile 0.6%