Add long-running connection stability test with dynamic token renewal

[Copilot]

Proposed changes

Implements a 90-minute nightly test validating OPC UA connection stability, subscription reliability, and security token renewal under extended runtime. Security token lifetime is dynamically configured based on environment to optimize testing for both CI and local development.

Test Implementation (ConnectionStabilityTest.cs)

• Single client session with subscription monitoring test nodes
• Separate writer session continuously updating values (2s interval)
• Tracks notification delivery, reports status every 60s
• Validates ≥95% notification delivery (allows network variance)
• Duration: TEST_DURATION_MINUTES env var (default: 90min CI, 1min local)
• Security token lifetime (dynamic):
  • CI: 5 minutes (300,000 ms) → 18 renewals in 90-minute test
  • Local: 10 seconds (10,000 ms) → 6 renewals in 1-minute test

GitHub Actions Workflow (stability-test.yml)

• Nightly execution: 2:00 AM UTC (cron)
• Manual dispatch with configurable duration
• 120-minute workflow timeout
• Explicit permissions: contents: read
• Uploads test results as artifacts

Documentation

• Added workflow status badge to README.md

Types of changes

• Test enhancement (non-breaking change to increase test coverage)

Checklist

• I have read the CONTRIBUTING doc.
• I have signed the CLA.
• I ran tests locally with my changes, all passed.
• I fixed all failing tests in the CI pipelines.
• I fixed all introduced issues with CodeQL and LGTM.
• I have added tests that prove my fix is effective or that my feature works and increased code coverage.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

Further comments

The dynamic token lifetime configuration optimizes testing for both environments:

• CI (90 min, 5-min tokens): 18 renewal cycles thoroughly stress the renewal mechanism, catching race conditions, memory leaks in channel recreation, and session recovery issues that only manifest under sustained load
• Local (1 min, 10-sec tokens): 6 renewal cycles provide quick validation while still exercising token renewal logic without requiring long test runs

Test validates:

• Connection stability over extended sessions
• Security token renewal mechanism under load (18 renewals in CI, 6 renewals locally)
• Subscription message delivery reliability (no notification loss)
• Memory stability (no leaks from continuous operation)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Need a long running test that verifies connection stability.</issue_title>
<issue_description>- use UA client and ia server in a single test that runs for a configurable duration

• test ensures no message loss, ie. Values received as expected.
• create a GitHub action runner configuration that runs the test for 90 minutes every night. Add a badge that shows passing on readme.md</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Long running tests need to pass #3423

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ romanett
❌ Copilot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[marcschier]

@copilot make it so that the token renewal also happens at least 5-6 times when not running the test as long running test

[Copilot]

@copilot make it so that the token renewal also happens at least 5-6 times when not running the test as long running test

Updated the non-CI default duration from 1 minute to 30 minutes, which allows for 6 token renewals (30 minutes ÷ 5-minute token lifetime = 6 renewals). The change is in commit e72f4d3.

[marcschier]

@copilot please keep the length at 1 minute for non ci, but configure the token renewal in this case with 10 seconds.

[Copilot]

@copilot please keep the length at 1 minute for non ci, but configure the token renewal in this case with 10 seconds.

Updated the test configuration:

• Local test duration: 1 minute (reverted from 30 minutes)
• Token renewal for local: 10 seconds
• This gives 6 token renewals in local testing (60 seconds ÷ 10 seconds = 6 renewals)
• CI remains unchanged: 90 minutes with 5-minute token renewal (18 renewals)

The change is in commit 76e2b27.

[romanett]

Works fine after my fix and produces the expected number of successful token renewals.