• Supported Browsers
• Packages
  • Status
• Internationalization (I18n)
• Contributing
• Local Development
• Local Development using Docker (Dev Containers)
• LICENSE

Terra Package	Version	Status	Dependencies
terra-clinical-data-grid
terra-clinical-detail-view
terra-clinical-header
terra-clinical-item-collection
terra-clinical-item-display
terra-clinical-item-view
terra-clinical-label-value-view
terra-clinical-onset-picker

Terra Package	Version	Status
terra-clinical-action-header
terra-clinical-app-delegate
terra-clinical-error-view
terra-clinical-modal-manager
terra-clinical-no-data-view
terra-clinical-site
terra-clinical-slide-group

Please review Terra's Internationalization documentation for more information. Included are directions on consumption and how internationalization is setup.

Please read through our contributing guidelines. Included are directions for issue reporting and pull requests.

1. Install docker https://www.docker.com/ to run browser tests.
2. Install dependencies and run tests.

npm install
npm run test

1. Install Docker.
2. Install Microsoft VS Code
3. Clone this repo.
4. Open this repo in VS Code.
5. Install the Dev Container extension.
   • Navigate to View -> Extension -> Search for and install Dev Containers (or "ms-vscode-remote.remote-containers")
   • More information on Dev Containers
6. Build the dev container.
   • Make sure you are connected to the Cerner VPN when building this container the first time.
   • Navigate to View -> Command Palette -> Open Workspace In Container or Reopen In Container.
7. You're now running in a dev container. Use the terminal of the dev container to issue any npm commands.
8. Before running any WDIO tests, make sure to perform the following steps:
   • Open a new terminal (outside the dev container) and navigate to ".devcontainer/" path in your repository.
   • Execute the command "docker compose -f docker-compose-wdio.yml up". Selenium hub should spin up. Leave this running in the background. If you see errors saying "container name already exists", run "docker container prune" command followed by pressing "y" to clear up any unused containers and try running the previous command again.
   • You can now run npm run test:docker or npm run wdio:docker commands to run WDIO tests from inside the Dev Container.
   • NOTE: Optionally, if you want to run other WDIO commands in the dev container, you can also edit the root package.json file WDIO scripts to include --disableSeleniumService=true flag. This will disable the selenium service from spinning up again. For example:

     "scripts": {
      "wdio-lowlight": "terra wdio --disableSeleniumService=true --themes clinical-lowlight-theme"
      }

Copyright 2017 - 2020 Cerner Innovation, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.