LogoLogo
  • Planet 4
  • Development
    • Contribute
    • Installation
    • Git Guidelines
    • Coding Standards
    • Continuous Delivery
  • CI/CD
    • Test Instances
    • Deployment
    • Testing
      • End-to-end Tests
      • Visual Regression Tests
  • NRO Customization
    • Development
      • Using Child Themes
      • Package Registry
      • Plugins
    • Testing
      • Visual Regression Tests
    • Deployment
      • Production
      • DB/Media Sync
  • Infrastructure
    • NRO Generation
    • ElasticSearch
    • Cloudflare
  • Recipes
    • Maintenance page
    • Production sync
    • Running commands
  • Platform
    • Practices
    • ADRs
      • [ADR-0001] Use Gitbook for Technical Documentation
      • [ADR-0002] P3 Archive elastic search integration
      • [ADR-0003] WYSIWYG Blocks Architecture
      • [ADR-0004] Switch to Monorepo
      • [ADR-0006] Define scope for deployment environments
      • [ADR-0008] PSR-4 Autoloading Standard
      • [ADR-0009] Include Media Library in master theme
      • [ADR-0011] PHP Coding Standards
      • [ADR-0012] Use custom SCSS syntax for variables
      • [ADR-0013] Choose a ticketing system
      • [ADR-0014] Choose a testing framework
      • [ADR-0015] Use block templates to build block patterns
      • [ADR-0016] Form Builder data retention policy
      • [ADR-0017] Move blocks into the theme
    • Changelog
      • 2024
      • 2023
      • 2022
      • 2021
      • 2020
      • 2019
      • 2018
  • Tech
    • Wordpress
    • Blocks
    • Plugins
    • Hooks
    • Data migrations
    • CSS variables
Powered by GitBook
On this page
  • Pull Requests
  • How to manually pick one
  • Data reset
Edit on GitHub
  1. CI/CD

Test Instances

Our Test Swarm for testing and doing UAT

PreviousContinuous DeliveryNextDeployment

Last updated 1 year ago

In order to test new code, but also to help requestors do UAT, we have created a swarm of test instances that can be used by P4 dev team to test and showcase specific changes.

Pull Requests

On opening a Pull Request a test instance is automatically selected. A label and a comment are added to the PR once it's been deployed. The relevant Jira ticket is also update in order for the test instance to appear occupied in the .

How to manually pick one

If you want to manually reserve a test instance you can follow these steps:

  1. Check the for an available instance. Available instances are colored green, instances currently in use are colored red.

  2. Go to your Jira ticket and enter the name of the instance you want to use in the environment field of the relevant ticket. This is necessary in order to reserve that instance. Keep in mind, that the ticket should be either "In Progress" (status "In Development") or "In Review".

  3. The Dashboard provides direct link to the instance source code, so by adjusting its composer-local.json file you can trigger a deployment for a specific branch per repository.

Data reset

When a PR is finally merge into the main branch of an app repository, a reset-instance job is running that mainly does two things:

  1. Adjusts composer-local.json and switch to dev-main for both app repositories.

  2. During the reset pipeline the defaultcontent database is being imported effectively reseting all addinional content that had been created in the meantime.

If you want to manually reset a test instance database all you have to do is add a commit with the [RESET] prefix in its subject.

Test Swarm Dashboard
Test Swarm Dashboard