-
Notifications
You must be signed in to change notification settings - Fork 69
/
tests.yml
91 lines (75 loc) · 3.15 KB
/
tests.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
# If any of these test names get updated they need to be updated here too
# https://github.com/department-of-veterans-affairs/va.gov-cms/settings/branches
version: '3'
dotenv: ['.env']
output: 'group'
tasks:
# Any changes to test names or additions or removals must be updated in
# .github/workflows/set-tugboat-tests-pending.yml as well for the
# test to be required effectively.
# The following is necessary to ensure that the tests are set to "pending"
# when the staging post-deploy tests start. If the tests are not all set to
# pending, then there is a chance that the auto deploy Jenkins job will check
# and only see the status of the tests that have completed so far, and so see
# a "success" status, and then auto deploy. This is a problem because the
# tests that have not yet completed may fail, and so the auto deploy will
# deploy a broken site.
set-deploy-tests-pending:
deps:
# Any changes to test names or additions or removals above must be updated here as well for the Pending status to work.
- task: set-check-status
vars:
STATUS: pending
CONTEXT: va/tests/cypress
DESCRIPTION: 'Cypress Accessibility/Behavioral'
- task: set-check-status
vars:
STATUS: pending
CONTEXT: va/tests/phpunit
DESCRIPTION: 'PHPUnit'
- task: set-check-status
vars:
STATUS: pending
CONTEXT: va/tests/status-error
DESCRIPTION: 'Check for Drupal status errors'
- task: set-check-status
vars:
STATUS: pending
CONTEXT: va/tests/content-build-gql
DESCRIPTION: 'Ensure that the content build graphql queries succeed'
va/tests/cypress:
desc: Accessibility and Behavioral tests with Cypress
# See also `composer va:test:cypress-parallel` in composer.json
# For local (e.g. DDEV) use, invoke `composer va:test:cypress`.
# For interactive use, invoke `composer va:test:cypress-interactive`.
cmds:
- ./tests/scripts/ci-wrapper.sh cypress 'va:test:cypress-parallel'
va/tests/phpunit:
desc: PHPUnit
# See also `composer va:test:phpunit-functional` in composer.json
cmds:
- ./tests/scripts/ci-wrapper.sh phpunit 'va:test:phpunit-functional'
va/tests/status-error:
desc: Check for Drupal status errors
# See also `composer va:test:status-error-ci` in composer.json
# For local (e.g. DDEV) use, invoke `composer va:test:status-error`.
cmds:
- ./tests/scripts/ci-wrapper.sh status-error 'va:test:status-error-ci'
va/tests/content-build-gql:
desc: Ensure that the content build graphql queries succeed
# See also `composer va:test:content-build-gql` in composer.json
cmds:
- ./tests/scripts/ci-wrapper.sh content-build-gql 'va:test:content-build-gql'
set-check-status:
cmds:
- |
if [ "$SKIP_REPORTING" -ne 1 ]; then
github-status-updater -action=update_state -state="{{ .STATUS }}" -context="{{ .CONTEXT }}" -description="{{ .DESCRIPTION }}"
fi
default:
desc:
deps:
- va/tests/cypress
- va/tests/phpunit
- va/tests/content-build-gql
- va/tests/status-error