mailstrom/.github/workflows/nightly-integration-tests.yml at 00b193853523a63cf1010004d5a55101b7ebe8ce · thunderbird/mailstrom · GitHub

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
92
93
94
95
96
97
98
99
100
name: nightly-integration-tests

concurrency:
  group: nightly-integration-tests
  cancel-in-progress: true

on:
  schedule:
    # run every day at 2am UTC (9PM EST)
    - cron:  '0 2 * * *'
  # allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

permissions:
  contents: read # required for actions checkout

jobs:
  nightly-integration-tests:
    name: nightly-integration-tests
    # github actions ubuntu runners have known intermittent network timeout / connection issues
    # (i.e. https://github.com/actions/runner-images/issues/11886) that cause the integration tests
    # to fail with intermittent connection reset issues; so we use macos runners instead
    runs-on: macos-latest
    environment:
      name: staging
      deployment: false
    env:
      IS_CI_AUTOMATION: "yes"
      TEST_SERVER_HOST: ${{ secrets.TEST_SERVER_HOST }}
      TEST_ACCT_1_USERNAME: ${{ secrets.TEST_ACCT_1_USERNAME }}
      TEST_ACCT_1_PASSWORD: ${{ secrets.TEST_ACCT_1_PASSWORD }}
      TEST_ACCT_1_EMAIL: ${{ secrets.TEST_ACCT_1_EMAIL }}
      TEST_ACCT_2_USERNAME: ${{ secrets.TEST_ACCT_2_USERNAME }}
      TEST_ACCT_2_PASSWORD: ${{ secrets.TEST_ACCT_2_PASSWORD }}
      TEST_ACCT_2_EMAIL: ${{ secrets.TEST_ACCT_2_EMAIL }}

    steps:
      - uses: actions/checkout@v5

      - name: Set up Python
        uses: actions/setup-python@v6
        with:
          python-version: '3.13.0'

      - name: Install test dependencies
        run: |
          python -m venv .venv
          source .venv/bin/activate
          python -m pip install --upgrade pip
          pip install ."[dev]"

      - name: JMAP integration tests
        continue-on-error: true # we want all tests to run even if these or others fail
        run: |
          source .venv/bin/activate
          cd test/integration
          cp .env.test.example .env.test
          python -m pytest jmap/ --junit-xml=./jmap-test-results.xml -vs

      - name: IMAP integration tests
        continue-on-error: true # we want all tests to run even if these or others fail
        run: |
          source .venv/bin/activate
          cd test/integration
          cp .env.test.example .env.test
          python -m pytest imap/ --junit-xml=./imap-test-results.xml -vs

      - name: SMTP integration tests
        continue-on-error: true # we want all tests to run even if these or others fail
        run: |
          source .venv/bin/activate
          cd test/integration
          cp .env.test.example .env.test
          python -m pytest smtp/ --junit-xml=./smtp-test-results.xml -vs

      - name: CalDAV integration tests
        continue-on-error: true # we want all tests to run even if these or others fail
        run: |
          source .venv/bin/activate
          cd test/integration
          cp .env.test.example .env.test
          python -m pytest caldav/ --junit-xml=./caldav-test-results.xml -vs

      - name: CardDAV integration tests
        continue-on-error: true # we want all tests to run even if these or others fail
        run: |
          source .venv/bin/activate
          cd test/integration
          cp .env.test.example .env.test
          python -m pytest carddav/ --junit-xml=./carddav-test-results.xml -vs

      - name: Create results report
        continue-on-error: true # we always want this step to run
        if: always()
        uses: pmeier/pytest-results-action@main
        with:
          path: test/integration/*test-results.xml
          summary: true
          fail-on-empty: false
          title: Mailstrom Integration Test Results