From 66738d8273ad2b08d5cc9a9518d497034b451c8a Mon Sep 17 00:00:00 2001 From: Tommy Gatti Date: Tue, 18 Jun 2024 16:08:30 +1000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: jo-basevi --- README-DEV.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README-DEV.md b/README-DEV.md index 2bfddf5..149cc1e 100644 --- a/README-DEV.md +++ b/README-DEV.md @@ -26,9 +26,9 @@ This dispatchable workflow allows developers to generate and commit initial chec This is the `config/ci.json` configuration file for specifying different test markers, or test versions based on type of the test to run, and the name of the git branch or tag. The different types of test are defined as: -- `scheduled`: These are scheduled monthly reproducibility tests that are run as part of [`schedule-2-start.yml`](#scheduled). The keys under these tests represent released config tags to run scheduled checks on. -- `reproducibility`: These are reproducibility tests are run as part of [`pr-1-ci.yml`](#pull-request). The keys under these tests represent the target branches into which pull requests are being merged. -- `qa` - These are quick QA tests are run as part of [`pr-1-ci.yml`](#pull-request). The keys under these tests represent the target branches into which pull requests are being merged. +- `scheduled`: Scheduled monthly reproducibility tests. The keys under these tests represent released config tags to run scheduled checks on. +- `reproducibility`: Reproducibility tests that are run as part of pull requests. The keys under these tests represent the target branches into which pull requests are being merged. +- `qa` - Quick quality assurance tests that are run as part of pull requests. The keys under these tests represent the target branches into which pull requests are being merged. The configuration properties needed to run the tests are: @@ -38,6 +38,6 @@ The configuration properties needed to run the tests are: | model-config-tests-version | `string` | The version of the model-config-tests | `0.0.1` | | python-version | `string` | The python version used to create test virtual environment | `3.11.0` | -As most of the tests use the same test and python versions, and similar markers, there are two levels of defaults. There's a default at test type level which is useful for defining test markers - this selects certain pytests to run in `model-config-tests`. There is an outer global default, which is used if a property is not defined for a given branch/tag, and it is not defined for the test default. The `parse-ci-config` action applies the fall-back default logic. For more information on using this action see [`parse-ci-config` README.md](./.github/actions/parse-ci-config/README.md). +As most of the tests use the same test and python versions, and similar markers, there are two levels of defaults. There's a default at test type level which is useful for defining test markers - this selects certain pytests to run in `model-config-tests`. There is an outer global default, which is used if a property is not defined for a given branch/tag, and it is not defined for the test default. The `parse-ci-config` action applies the fall-back default logic. For more information on using this action see [`ACCESS-NRI/model-config-tests`](https://github.com/ACCESS-NRI/model-config-tests/). The CI for this file (in [`config.yml`](./.github/workflows/config.yml)) validates modifications to the `ci.json` against it's schema, found in [`ACCESS-NRI/schema`](https://github.com/ACCESS-NRI/schema). It does not yet verify that modifications make sense.