TST Meeting Minutes 2026

[PiotrKorkus]

Please be invited to join our testing community discussions during Eclipse S-Core Testing Team meeting.

Join Zoom Meeting

[PiotrKorkus]

Meeting minutes 07.01.2026:

Participants:

Andreas @anmittag
Leonardo @odra
Piotr @PiotrKorkus
Philipp @pahmann
Tobi @tbreckle

SCORE 0.5-beta release:

https://github.com/eclipse-score/reference_integration/releases/tag/v0.5.0-beta

---

Please check any issues assigned to you - stale, obsolete, missing description, etc.

[PiotrKorkus]

Meeting minutes 14.01.2026:

Participants:

Leonardo @odra
Piotr @PiotrKorkus

Agenda:

• S-Core release scheduling update
• ITF tests capturing DLTs by LTTS colleagues
• VIPER presentation will take place next week VIPER Presentation #2429
• SCTF status

[PiotrKorkus]

Meeting minutes 28.01.2026:

Participants:

Alexander @AlexanderLanin
Ali @fares-a-n
Leonardo @odra
Philipp @pahmann
Piotr @PiotrKorkus
Saumya @Saumya-R
Tobi @tbreckle

Agenda:

• ITF tests capturing DLTs by LTTS colleagues
• Traceability dashboard - process-wise review: testlinks, naming, bi-direction?
  docs: requirements statistics dashboard persistency#232
  https://eclipse-score.github.io/persistency/pr-232/persistency/kvs/docs/requirements/statistics.html
• Testing definitions reading from Alexander:
  https://gist.github.com/AlexanderLanin/daba32bb4cf0e8683216cbcb97c8bd33

[PiotrKorkus]

Meeting minutes 04.02.2026:

Participants:

Piotr @PiotrKorkus
Philipp @pahmann

Agenda:

• Feature Integration Test traceability in reference_integration established locally. Working on combo docs with CITs results.
• SWEBOOK

[pahmann]

Meeting minutes 11.02.2026:

Participants:

Philipp Ahmann @pahmann
Dragan Bjedov @draganbjedov
Maciej Kaszynski @MaciejKaszynski
Rachele Setto @RacheleSetto
Maximilian Sören Polak @MaximilianSoerenPollak
Andreas Mittag @anmittag

Regrets:

Piotr @PiotrKorkus

Agenda:

• Check pending items from the past
• ❌ Safety audit findings related to verification: Fix Verification Audit Findings process_description#566 --> topic for next meeting
• ✅ Piotr: Feature Integration Test traceability in reference_integration established locally. Working on combo docs with CITs results.
• ✅ ITF -> will there be a release for SCORE 0.6?
• ✅ release checklist Checklist v0.6 #2564
• ✅ AoB = Any other business
  • ✅ SWEBOOK

Minutes

• ITF -> will there be a release for SCORE 0.6?
  • Refactoring, DLT is now a test plugin, no longer default as it was in the past
  • Qemu as pytest plugin.
  • Changes that ITF is independent on target qemu, docker, real HW, ... it should become agnostic.
  • Changes are considered for 0.7 as 0.6 integration is currently going on.
  • For v0.6 the 0.1 is the version to be released (constant to last milestone)
• Feature Integration Test traceability in reference_integration established locally. Working on combo docs with CITs results.
  • test executed which are either in reference_integration and different module like persistency.
  • when they are referenced and linked to requirements they pop up
  • Currently locally tested, but of course dependent on module implementation.
  • Not yet properly working for rust. Existing solution is quite heavy, so maybe something tailored by infrastructure team is considered.
• release checklist Checklist v0.6 #2564
  • need to check that there is a tick box for component and feature integration tests.
• AoB
  • Lifecycle wants to make use of ITF. Directory structure change (reorganization), but base implementation remains stable and use case is the same. So Lifecycle can start looking into writing ITF tests.
  • Some people from Logging also start writing ITF test cases.
  • Binary testing in lifecycle. Use https://github.com/eclipse-score/os_images to create own qemu image.
    • Final integration will be of course done on reference integration repo.
  • how does forking work to have a repo part of S-CORE
    • make a new repository and specify that you are a fork.
    • https://github.com/eclipse-score/.eclipsefdn/blob/main/otterdog/eclipse-score.jsonnet#L988-L1008
    • Tech lead from S-CORE and security/otterdog team from Eclipse have to approve a new fork.
    • Use case is the GENIVI/COVESA DLT and ITF currently depends on another fork, which should be brought into S-CORE for proper maintenance within the project.
  • SWEBOOK
    • Good read around all software engineering topics and also has a lot around verification and testing.

[PiotrKorkus]

Meeting minutes 18.02.2026:

Participants:

Piotr @PiotrKorkus
Tobi @tbreckle
Chris @clanghans
Ali @fares-a-n

Agenda:

• Safety audit findings related to verification: Fix Verification Audit Findings process_description#566 --> topic for next meeting
• Release checklist Checklist v0.6 #2564
• Reference integration current state

Minutes

• release checklist Checklist v0.6 #2564
  • added example to PR triggering tests in reference integration
• updates in reference integration:
  • dashboard with UT summary and code coverage
  • all modules are automatically tested with UTs execution and coverage calculation for C++
  • rust coverage is the next goal
• test scenarios are always a dependency in a module that uses it meaning they are build with the toolchains from tested module itself
• DLT & ITF examples are still getting finalized

[PiotrKorkus]

Meeting minutes 25.02.2026:

Participants:

Piotr @PiotrKorkus
Chris @clanghans
Rachele @RacheleSetto
Ali @fares-a-n
Anamika

Agenda:

• Release v0.6 finished https://github.com/eclipse-score/reference_integration/releases/tag/v0.6.0
• Improvement Backlog for v0.7 Improvements for release v0.7 reference_integration#121
• Set dev_depenency True for rules_oci itf#53

Minutes

• SCTF won't be released to SCORE - ITF with docker plugin provides the same functionality
• coverage reports - added rust, trend plots won't be supported, further work on including detailed reports
• detailed coverage reports are attached to the SCORE release assets
• ITF in reference_integration will be updated this week to use newest main

[pahmann]

Meeting minutes 04.03.2026:

Participants

Piotr @PiotrKorkus
Philipp @pahmann
Leonardo @odra
Volker @PandaeDo
Anamika @AnaMaheshwari
Max @MaximilianSoerenPollak
Alexander @AlexanderLanin

Agenda

1. How to see that coverage for testing a single requirement is complete?
   1. What about having test suites which execute several tests with partial coverage?
   2. This could lead to multiple executions of a single test cases when performing a full run?
   3. Also a collect test case results test case could help, but this defines an execution order to happen.
   4. What practical solutions do the people bring? How to proceed?
2. help/input from testing to acceptance criteria / metrics
3. Please review release process: docs: release process documentation reference_integration#168

Minutes

Audit review:

• fully-tested keyword
• manual confirmation that multiple-partially verifies is sufficient e.g. additional test collecting partially-verifies test-cases @PiotrKorkus to create a ticket for that

eclipse-score/process_description#561 (comment)

Not discussed (posted by Alexander):

[PiotrKorkus]

Meeting minutes 11.03.2026:

Participants

Piotr @PiotrKorkus
Volker @PandaeDo
Rachele @RacheleSetto
Chris @clanghans
Max @MaximilianSoerenPollak
Frank @FScholPer
Alexander @AlexanderLanin

Agenda

• ITF changes
• UTs for Rust onepager

Minutes

• ITF tests in ref_int can now use images from external os repo. No longer need to duplicate images across different repositories.
  Initial QNX8 QEMU images for x86_64 and arm64 os_images#5
  ITF PR incoming
• Rust branch and statement coverage status to be checked and merging rust html reports into single one
• Release process description #2671
• Reusable on PR workflow (single one)
  https://github.com/eclipse-score/cicd-workflows/blob/dev/.github/workflows/reusable-on-pr.yml
• switch repos' workflows from @main to @v0.0.0
• start using mapping for UTs to establish metrics (not possible unless there are HLD requirements)

[PiotrKorkus]

Meeting minutes 18.03.2026:

Participants

Piotr @PiotrKorkus
Volker @PandaeDo
Philipp @pahmann
Anamika @AnaMaheshwari
An Dao @nhuvaoanh123

Agenda

• verification report discussion
• merge cicd-workflows pinning to the version ASAP
• approval workflow Workflow gathering approvals on release branch reference_integration#189
• fill bazel_registry metadata in your modules
• is os_images currently ready to use? Initial QNX8 QEMU images for x86_64 and arm64 os_images#5

Minutes

• https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/guidance/requirements_process_reqs.html#gd_req__req_attr_test_covered
  attribute can be set after tests are merged, feature requirements are located in different repo so 2nd PR is needed
  when req is changing we change YES->NO
  rephrase test_covered
• observed first issues with using docs workflow directly from @main

[PiotrKorkus]

Meeting minutes 25.03.2026:

Participants

Piotr @PiotrKorkus
Saumya @Saumya-R
Rachele @RacheleSetto
Anamika @AnaMaheshwari

Agenda

• itf traceability plugin
• https://eclipse-score.github.io/infrastructure/chapters/03-testing-infrastructure/
• is os_images currently ready to use? Initial QNX8 QEMU images for x86_64 and arm64 os_images#5

Minutes

• add_test_properties decorator can be used with ITF now
• https://eclipse-score.github.io/infrastructure/chapters/03-testing-infrastructure/ - feel free to go through it and share any comments, it is still under development
• QNX will be contacted tomorrow again for the new release which is enabler for ITF update

[AnaMaheshwari]

yes ..seems i only have read access but i want to create branch or draft PR for system ITF test then i don't have write access

[PiotrKorkus]

https://eclipse-score.github.io/score/main/contribute/contribution_request/index.html#doc__contr_guideline

You need to create a PR from your company (preffered) or private fork.

[AnaMaheshwari]

from LTTS (company)

[AnaMaheshwari]

I have already signed ECA

[PiotrKorkus]

so push your branch to company fork and create a PR from fork to upstream

[PiotrKorkus]

Meeting minutes 01.04.2026:

Participants

Piotr @PiotrKorkus
Leonardo @odra

Agenda

• Add rust support qnx_unit_tests#11
• ongoing FIT transfer to ITF in reference_integration
• ITF support for AutoSD

Minutes

• QNX UTs targets have been published, allow running both C++ and Rust tests. There is planned support for arm64 and --run-under option.
• Leonardo is working on enabling ITF to run tests on AutoSD

[PiotrKorkus]

Meeting minutes 08.04.2026:

Participants

Piotr @PiotrKorkus
Leonardo @odra
Chris @clanghans
Philipp @pahmann
Alexander @AlexanderLanin
Ante @antres1
Anamika @AnaMaheshwari
Iheb

Agenda

• Decision record - reference_integration scope #2747 (review)

Minutes

• Reference_integration will most likely continue with option 3 from decision record. Only FITs and additional dependency resolving checks will be executed in ref_int. Other tests will be executed directly in Modules and part of releases' assets.
• https://eclipse-score.github.io/infrastructure/04-testing-infrastructure/ please review and feel free to propose updates.

[PiotrKorkus]

Meeting minutes 15.04.2026:

Participants

Piotr @PiotrKorkus
Volker @PandaeDo
Rachele @RacheleSetto
Ante @antres1

Agenda

• QNX UTs targets are executable under qnx aarch64
• Release v0.7 initial scope
• Rework qemu startup/configuration itf#83

Minutes

• QNX unit tests were updated - now aarch64 is supported. https://github.com/eclipse-score/qnx_unit_tests/ . To be utilized for v0.8 release.
• Release will follow approach for v0.6, no major updates expected. Checklist for each Module to be defined tomorrow.
• ITF update redesigning Qemu startup, makes uitilization of os_images repository. Configs are stored as json files. Allows ITF to start Qemu simulation with given os_image and architecture. Pull request in reference_integration is still internal, to be published later.

[PiotrKorkus]

Meeting minutes 22.04.2026:

Participants

Piotr @PiotrKorkus
Chris @clanghans
Volker @PandaeDo
Rachele @RacheleSetto

Agenda

• Release v0.7
• codeql update
• ITF & HW testing

Minutes

• Release will take place on 04.05. No changes to the testing approach due to DR008 not completed. Builds, UTs, docs will be executed in reference_integration together with FITs for the artifacts collection.
• CodeQL workflow has been updated - checks correct revisions based on known_good file and doesn't include warnings from unwanted repositories.
• OpenDUT is explored locally to check its capabilities in integrating private labs into SCORE validation.

[AlexanderLanin]

Meeting minutes 06.05.2026:

Participants

@clanghans
@PandaeDo
@RacheleSetto
@pahmann
@AlexanderLanin
@jgetas

Agenda

• request for comments: Test use cases and QNX environments
• code coverage runner migration Ubuntu 22 -> 24
• SCORE v0.7 update

Minutes

• Please review and put your comments under QNX env discussion
• due to code coverage calculation issues for release candidate v0.7 workflow will be switched to pull_request trigger for the time of the release and then restored to pull_request_target after release next week

[PiotrKorkus]

Meeting minutes 13.05.2026:

Participants

@PandaeDo
@RacheleSetto
@jgetas
@JanStaschulat
@clanghans

Agenda

• SCORE v0.7 has been released
• v0.8 gap identification

Minutes

• reference_integration repo has the versions from v0.7 merged to main, workflows are restored and access to secrets from forks is possible
• https://eclipse-score.github.io/process_description/pr-675/standards/feature_and_process_status.html#process-area-5-verification

[PiotrKorkus]

Meeting minutes 20.05.2026:

Participants

@PiotrKorkus
@ltekieli
@PandaeDo
@pahmann
@clanghans
@JanStaschulat
@tbreckle

Agenda

• QNX UT presentation https://github.com/eclipse-score/qnx_unit_tests
• testing backlog review

Minutes

• QNX UT presentation - dedicated framework for running UTs on QNX. It is separate thing from ITF. Supports regular bazel test commands, parallel tests, no need to specify qemu configs.
• current backlog: TST - Testing Community (view)
• Review requests:
  feat(test): add unit test infrastructure with py_itf_unittest itf#94
  docs(decisions): add DR-001 for unit test design itf#105

[PiotrKorkus]

Meeting minutes 27.05.2026:

Participants

@PiotrKorkus
@AlexanderLanin
@pahmann
@RacheleSetto
@JanStaschulat

Agenda

• QNX rust coverage problems with .profraw generation
• testing backlog review
• verification report

Minutes

• When ferrocene coverage config is added to qnx unit test they do not build correctly. Updates needed to make it compatibile with qnx.
• Alex is preparing tutorial how to implement tests - https://eclipse-score.github.io/infrastructure/main/tutorials/write-a-test.html
• Discussed verification report naming and storing conventions - release notes shall point to specific report not "latest"
• Feedback from the Technical Lead Circle (see https://github.com/orgs/eclipse-score/discussions/516#discussioncomment-16927020): Verification Report was worked on in different initiatives. There is something implemented in docs-and-code: https://eclipse-score.github.io/docs-as-code/main/how-to/dashboards_and_quality_gates.html - TLs will decide how to pilot and implement this approach (based on the verification report template - https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_report_template.html)

[PiotrKorkus]

Meeting minutes 03.06.2026:

Participants

@PiotrKorkus
@AlexanderLanin
@JanStaschulat
@pahmann
@Saumya-R

Agenda

• testing backlog review
• verification report

Minutes

• the GH Pages have limit 100mb, not a problem for now can be optimized in the future to store multiple release notes
• Content of _build should be uploaded to release assets as well not only gh_pages branch - @MaximilianSoerenPollak
• Alex is preparing tutorial how to implement tests - https://eclipse-score.github.io/infrastructure/main/tutorials/write-a-test.html
  https://eclipse-score.github.io/infrastructure/main/how-to/testing.html
• FITs are getting bigger - reflect on the location, shall they still be a part of reference_integration repository, module's repo itself or a new separate location?
• Please review:
  Add QNX8 aarch64 build support reference_integration#241
  Update README with QNX8 aarch64, RPi showcase guide, and existing docs improvements reference_integration#246
  Lifecycle Feature Integration Tests  reference_integration#238

[PiotrKorkus]

Meeting minutes 10.06.2026:

Participants

@PiotrKorkus
@PandaeDo
@JanStaschulat
@clanghans
@AlexanderLanin
@Saumya-R

Agenda

• MISRA in ref_int
• bazel coverage
• PRs stuck in ITF

Minutes

• upload sarif results to security tab reference_integration#260
  @AlexanderLanin will disable default config for reference_integration in otterdog. This should enable uploading result to security tab.
• Coverage calculation for C++ and Rust reference_integration#259
  there will be separate meeting next week to discuss common coverage configuration. Feel free to tag yourself if you want to participate. Input comments before meeting are welcome.
• Piotr to drop a message to Lukasz about pending reviews in ITF repository

[AlexanderLanin]

PR to disable default codeql config: eclipse-score/.eclipsefdn#195

[PiotrKorkus]

Meeting minutes 01.07.2026:

Participants

@PiotrKorkus
@PandaeDo
@pahmann
@clanghans

Agenda

• test specification for partially verified @pahmann
• llvm proposal from Comm

Minutes

• test specification for partially verified
  reference: https://github.com/orgs/eclipse-score/discussions/2234?sort=new#discussioncomment-17335819
  You can have test specification but without implementation yet - this should be described in process description @pahmann
  For the requirement verified by multiple partially_verified tests there is an optional field in requirement testcovered which can be set to YES to show the requirement is fully verified by the set of those test cases.

• llvm proposal from Comm
  reference: Coverage calculation for C++ and Rust reference_integration#259
  to be check if this solution can be also used for calculating coverage on QNX, as QNX toolchains are currently based on gcc.

[PiotrKorkus]

Meeting minutes 15.07.2026:

Participants

@PiotrKorkus
@anmittag
@clanghans

Agenda

• SCORE release v0.8 completed
• ITF Qemu plugins

Minutes

• SCORE release v0.8 completed
  Modules overall status: https://eclipse-score.github.io/reference_integration/v0.8.0/s_core_v_1/roadmap/overall_status.html

• ITF Qemu plugins
  Lutz proposed to add plugins for all missing images - aarch qnx, ubuntu, eb
  Check ITF roadmap if any of those are planned
  Currently repository os_images https://github.com/eclipse-score/os_images contains only autosd and other images like qnx x86, qnx aarch64 are located in reference_integration repo. All images should be moved to single place which is os_images, so other modules can benefit also from it.

[PiotrKorkus]

Meeting minutes 29.07.2026:

There were issues joining the meeting today:

[PiotrKorkus]

Meeting minutes 12.08.2026:

Participants

@PiotrKorkus
@clanghans

Agenda

Reviews:
eclipse-score/itf#123
eclipse-score/qnx_unit_tests#35
eclipse-score/qnx_unit_tests#37

[PiotrKorkus]

Meeting minutes 26.08.2026:

Participants

@PiotrKorkus
@pahmann
@odra
@clanghans

Agenda

• DR folder structure: Add DR about module folder structure #3194
• Module Verification Report demo: render module verification report via score_module_verification_report (tracks docs-as-code#730) baselibs#491

Minutes

• Test should have a separate directory but its location is not important. The frameworks can be configured to discover different paths and bazel targets can be aliased.
• Module verification report as single target might bring issues for different configurations needed to specific test targets. DaC got implementation that renders report based on the internal templates but it needs maintenance to keep in line with the process_description template.

[PiotrKorkus]

Meeting minutes 09.09.2026:

Participants

@PiotrKorkus

Agenda

• SCORE v0.9 release: https://github.com/eclipse-score/reference_integration/releases/tag/v0.9.0
• Pending Reviews: feat: Add QEMU disk image parameter itf#139

Minutes

[PiotrKorkus]

Meeting minutes 23.09.2026:

Participants

@PiotrKorkus

Agenda

• Modules should bump their hashes to newest main this week
• Pending Reviews: Bump imagefs reference_integration#349
• Feature Integration Tests location

Minutes

[antonkri]

Meeting minutes 21.10.2026:

Participants

@PiotrKorkus
@odra
@ihebs3ideni
@antonkri
@Saumya-R
@clanghans
@draganbjedov
@WachowskiM
@nick-hildebrant-etas

Agenda

• Further development & maintenance of ITF

Minutes

• presentation to be shared, I will add once available

[ihebs3ideni]

Attached are the presentations shown during the meeting
itf_mental_model.pdf
itf-score-pitch.pdf