Skip to content

Testing Environment Setup

Source: Onboarding RaaSv2.x — Configure Testing Env (TRIB 19707330884)

This page covers setting up the RaaS automated testing environment for a new customer. Tests run against the deployed infrastructure and validate the Rhapsody installation.

Step 1: Clone the Testing Repo

git clone git@github.com:rhapsody-health/testing-raas-v2.x.git
cd testing-raas-v2.x

Step 2: Create a Customer Branch

Branch off the appropriate base branch for the customer's environment:

git checkout {{customer_code}}-{{devops_env}}
git checkout -b RAAS-{{ticket}}-{{description}}

Step 3: Update .gitlab_ci Configuration

Edit the CI configuration to add the customer's details:

# Add to the customer_codes list
customer_codes:
  - uk-hscn

# Add to account ID mapping
account_ids:
  uk-hscn: "943397710386"

Step 4: Submit MR

  1. Push your branch
  2. Open a Merge Request targeting testing-raas-v2.x (the main branch)
  3. Request review from a senior engineer

Step 5: Run the Pipeline

Once merged, trigger the pipeline from GitLab. It will:

  1. Connect to the customer's AWS environment
  2. Run the automated test suite against the deployed RaaS instances
  3. Validate Rhapsody is installed, licensed, and running correctly
  4. Check networking, monitoring agents, and backup configuration

Step 6: Review Results

View all pipeline results and test reports at:

https://pipelines.raas.rhapsody.global/

Login with: firstname.lastname@lyniate.com

Note

If tests fail, check the pipeline logs for specific failure details. Common issues include: incorrect security group whitelist, missing DNS records, or Rhapsody not fully started after first boot.