Meeting Minutes #249

dneail1601 · 2025-01-29T13:42:49Z

dneail1601
Jan 29, 2025
Collaborator

Collaboration of all meeting minutes. Please mark changes of the notes.

dneail1601 · 2025-01-29T13:49:58Z

dneail1601
Jan 29, 2025
Collaborator Author

Meeting minutes 29.01.2025

Participants:
@julian711
@pahmann
@ltekieli
@draganbjedov
@dneail1601

#Start 15:32

Time -> Dragan move to 14:30
Length: Remains 30 minutes (Agreed)
Depending on topic separate meetings will be planned (if required)
Structure
    General issues organisation etc.
    Issues resolution (if required)
    Topics from last week
    Topics for next week (including unresolved topics)
Infrastructure
S-Core Incubator -> S-Core incubator migration (Dragan) Finished this week
Migrate ITF to S-Core -> Issue 169 Finished this week
Elaborate the testing process further with goal of producing a safety case (automatically) -> Proposal next week by Daniel -> In two weeks we discuss acceptance
Issues to be created only for Topics that require an Action or work product. Everything else is loose text in the meeting minutes.
Slack is set as communication tool with own channel
Add the chat to Github meeting minutes
Topics for next meeting:
    How to organize the documentation (alternative Slack conservation -> API) -> Daniel
    https://sdvworkinggroup.slack.com/archives/C08B6C78EF3
    https://sdv.eclipse.org/get-engaged/
    Source control -> -feature request
    Process Proposal SEooC
    (AP) adds another point to Github

#End 15:38

Chat:
Hello all, I am in the train, so focus on chat messages. (Means I reply on chat not via voice)

Slot is fine.

Bjedov Dragan, JC-12 (Unverified) has temporarily joined the chat.

We also got some findings from the interim on the verfication process. This I would like to see added to the agenda next week, when I have a good internet connection again.

https://github.com/eclipse-score/itf/pull/1/files
Basic ITF setup by draganbjedov · Pull Request #1 · eclipse-score/itf
Issue: #169

Last week we also aligned that hte selection reason for ITF will be explained again in this group

So far Testing was not really touch a lot as part of S-Core incubator.

There's some space already for discussion/meeting minutes:
https://github.com/orgs/eclipse-score/discussions/categories/testing-community

GitHub
GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

I would recommend make it an issue or just a note based on the size.

Feature Requests
Feature Requests • eclipse-score
Feature Requests

https://app.slack.com/client/T02MS1M89UH/C0894QGRZDM
Slack

Should we also create a dedicate score-testing slack channel?

Should I simply create #score-testing?

I created the channel and added Lukasz

I could not find the rest of you.

https://sdvworkinggroup.slack.com/archives/C08B6C78EF3
Slack

https://sdv.eclipse.org/get-engaged/
Get Engaged | The Eclipse Foundation
An open technology platform for the software defined vehicle of the future.

0 replies

dneail1601 · 2025-02-05T13:47:07Z

dneail1601
Feb 5, 2025
Collaborator Author

Meeting minutes 05.02.2025

Participants:
Lazlo
Julian
Dragan (left 1500)
Rebecca
Pacal
Lukasz
Thomas (1500)

#Start time: 15:32

Topics:
Time meeting for future shall be 14:30 in general ->General
-How to organize the documentation (alternative Slack conservation -> API) -> Daniel -> solved
Seperate the documentation in (Proposal and discussion) plus the offical agreed documentation. Work shall enter discussion first and enter offical path after general agreement in this testing meeting. Specific focused topics with expected/planned output shall be handled by a pull request. So the character of discussion is more generalized. The folders will be linked to the testing community. The testing documentation shall be linked to features or elements(modules) with testing focus.

-Slack for communication with own group: (solved)
Slack shall be only used for short coordination. Everything else shall be documented in Github. Agreed channel will be https://sdvworkinggroup.slack.com/archives/C08B6C78EF3. Everything that is deemed to be stored shall be transfered to Github (Discussion).

-Addtional Topic (OpenDUT) Pascal:
Possiblity introduction of OpenDUT into score. Proposal:
a) General meeting with introduction with example (Pascal + Thomas 30min) + 30min discussion -> Timing Slack Channel
b) Discuss offline
c) Follow up meeting for final discussion

-Usable Requirements are requested by ETAS to be able to evaluate/work with.

-Everybody is part of Eclipse, therefore https://sdv.eclipse.org/get-engaged/ (subscription to mailing lists etc.) is set.

-Process Proposal SEooC:
Will be added to the discussion topics. (Daniel)

-S-Core incubator move to S-Core see issue #169. No further follow up here.

-(AP) adds another point to Github -> Not discussed

Open Topics from last time:
How to organize the documentation (alternative Slack conservation -> API) -> Daniel
https://sdvworkinggroup.slack.com/archives/C08B6C78EF3
https://sdv.eclipse.org/get-engaged/
Source control -> -feature request
Process Proposal SEooC
(AP) adds another point to Github

Future Topics:
-Reach usable state for Requirements (completeness and tracebility).
-OpenDUT integration
-Specific Roadmap is required (proposal in discussion)
-Later integration of architectural constraints (Architecture by 1.4.2025). Tests shall be available before that regarding the structured input.
-Distribution and contribution shall be organized -> Project plan
-Personal capability and focus matrix (Not to be communicated pubilcy)

#End 15:43

Chat:
Daniel Klotz (Nicht überprüft) ist dem Chat vorübergehend beigetreten.
Benutzer Bjedov Dragan, JC-12 (Nicht überprüft) (Extern) ist vorübergehend dem Chat beigetreten.
Bjedov Dragan, JC-12 (Nicht überprüft) ist dem Chat vorübergehend beigetreten.
Benutzer Hirmer, Pascal (059) (Nicht überprüft) ist vorübergehend dem Chat beigetreten.
Hirmer, Pascal (059) (Nicht überprüft) ist dem Chat vorübergehend beigetreten.
Benutzer Tekieli Lukasz, JC-60 (Nicht überprüft) ist vorübergehend dem Chat beigetreten.
Tekieli Lukasz, JC-60 (Nicht überprüft) ist dem Chat vorübergehend beigetreten.
Benutzer Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) ist vorübergehend dem Chat beigetreten.
Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) ist dem Chat vorübergehend beigetreten.
Benutzer Irmscher Thomas (ETAS-SID/XPC-Mu) (Nicht überprüft) ist vorübergehend dem Chat beigetreten.
Irmscher Thomas (ETAS-SID/XPC-Mu) (Nicht überprüft) ist dem Chat vorübergehend beigetreten.
ntd x Bjedov Dragan, JC-12 (Nicht überprüft)
Bjedov Dragan, JC-12 (Nicht überprüft) (Extern)
15:00
ntd
General information about OpenDuT: Link ht... x Hirmer, Pascal (059) (Nicht überprüft)
Hirmer, Pascal (059) (Nicht überprüft)
15:03
General information about OpenDuT: https://opendut.eclipse.dev/
I need to jump to the next meeting, thank y... x Hirmer, Pascal (059) (Nicht überprüft)
Hirmer, Pascal (059) (Nicht überprüft)
15:30
I need to jump to the next meeting, thank you all, we will be in touch with the OpenDuT presentation
1 Gefällt mir-Reaktion.
Hirmer, Pascal (059) (Nicht überprüft) hat auf den Chat keinen Zugriff mehr.
Hirmer, Pascal (059) (Nicht überprüft) hat auf den Chat keinen Zugriff mehr.
Same for me. Thank you and see you soon x Irmscher Thomas (ETAS-SID/XPC-Mu) (Nicht überprüft)
Irmscher Thomas (ETAS-SID/XPC-Mu) (Nicht überprüft)
15:30
Same for me. Thank you and see you soon
1 Gefällt mir-Reaktion.
Irmscher Thomas (ETAS-SID/XPC-Mu) (Nicht überprüft) hat auf den Chat keinen Zugriff mehr.
Irmscher Thomas (ETAS-SID/XPC-Mu) (Nicht überprüft) hat auf den Chat keinen Zugriff mehr.
I need to drop, thanks x Tekieli Lukasz, JC-60 (Nicht überprüft)
Tekieli Lukasz, JC-60 (Nicht überprüft)
15:33
I need to drop, thanks
Tekieli Lukasz, JC-60 (Nicht überprüft) hat auf den Chat keinen Zugriff mehr.
Tekieli Lukasz, JC-60 (Nicht überprüft) hat auf den Chat keinen Zugriff mehr.
Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) hat auf den Chat keinen Zugriff mehr.
Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) hat auf den Chat keinen Zugriff mehr.
hat Kontextmenü

2 replies

dneail1601 Feb 5, 2025
Collaborator Author

Seems an invitation with email is required by Slack SW. @ltekieli cloud you send the invitations to the channel or add the Github emails?

julian711 Feb 6, 2025
Collaborator

The link to get access to the Slack workspace is given at the meeting minutes above: https://sdv.eclipse.org/get-engaged/

pahmann · 2025-02-12T08:12:34Z

pahmann
Feb 12, 2025
Collaborator

Options for WG meeting topics Feb 12th:

Audit findings wrt verification: Fix audit 2 findings process_description#2
openDUT meeting on Friday

0 replies

dneail1601 · 2025-02-12T14:32:37Z

dneail1601
Feb 12, 2025
Collaborator Author

Meeting minutes 12.02.2025

Participants:
Dragan
Lazlo
Julian
Alberto
Phillip
Lukaz

#Start time: 15:02

Remaining topics:
-Reach usable state for Requirements (completeness and tracebility). -> Start aproximately 1.4.2025 -> Late Requirements and Architcture
-OpenDUT integration -> 14.2.2025 presentation (Slack and email) -> Invitation via @markert-r (will invite, Phil will communicate)
-Specific Roadmap is required (proposal in discussion) -> Available in Qorix pubilc space (TBD add link)
-Later integration of architectural constraints (Architecture by 1.4.2025). Tests shall be available before that regarding the structured input.
-Distribution and contribution shall be organized -> Project plan
-Personal capability and focus matrix (Not to be communicated pubilcy) -> No matrix, volunteering for task/issues (done in meetings)

Future topics:

Formulate plan according to Feature Requests, github.com/orgs/eclipse-score/projects/5 -> @dneail1601
Demonstrator for test generator
ITF needs to be made available -> Dragan (open TBD, possible end May)
Setup/use for virtual environment

#End time 16:32

General Discussion:
Focus on verification shall be ASIL B (Phil, Julian)

possible Task:

Tasks will be generated according to ISO 26262 -> @dneail1601
Alberto: Possible tool from Matlab -> Polyspace

Chat:
Here is the openDut documentation: https://opendut.eclipse.dev/book/index.html (Someone was asking for it)
Introduction - openDuT

There is a dedicated usage guideline for AI generated code for Eclipse committers: https://www.eclipse.org/projects/guidelines/genai/
Generative Artificial Intelligence Usage Guidelines for Eclipse Committers | The Eclipse Foundation
The Eclipse Foundation - home to a global community, the Eclipse IDE, Jakarta EE and over 415 open source projects, including runtimes, tools and frameworks.

https://www.mathworks.com/products/polyspace-test.html
Polyspace Test
With Polyspace Test, you can develop, manage, and execute unit and integration tests for C/C++ code in embedded systems.

Sorry, I need to drop. Talk to you next week. It was a good discussion today!

Feature Requests
Feature Requests • eclipse-score
Feature Requests

Integration testing
Integration testing • eclipse-score
Integration testing

0 replies

dneail1601 · 2025-02-19T14:00:16Z

dneail1601
Feb 19, 2025
Collaborator Author

Meeting minutes 19.02.2025

Participants:
Lazlo
Alberto
Daniel
Phillip
Rebecca

#Start time: 15:02

Tasks:

Remains from last week:

Formulate plan according to https://github.com/orgs/eclipse-score/projects/4, github.com/orgs/eclipse-score/projects/5 -> @dneail1601
- Generic time plan created
Demonstrator for test generator
- Still under test and development
ITF needs to be made available -> Dragan (open TBD, possible end May)
- Expected to be in SCORE next week (functionality wise, step by step)
Setup/use for virtual environment -> Lukasz
- https://github.com/eclipse-score/score/issues/167
- Also expected for next week
Tasks will be generated according to ISO 26262 -> @dneail1601
- Tool Qualification justification (safety) first draft next week.
- First shot could be SDD from Code followed by a review
Alberto: Possible tool from Matlab -> Polyspace
- out of scope since commercial tool

Topic:
Automatic test case creation. Expected would be a 80:20 distribution. Goal is to have SDD and Arch, Design which is independent. Feature Request for the parsing to be created in S-CORE (transfer to S-CORE from Qorix > @dneail1601).

New Topics:

OpenDUT, currently out of scope. Possible beneficial for test parallelization and test distribution over multiple hardware devices (scaling). A feature request for usage and coordination between S-CORE and OpenDUT to be created. -> Alberto @Atm-Acn

Next week topics:

Reasoning for ITF Framework (Anton)
Planning, incorporate top level timelines (milestones etc.). Plan Sync meeting on monday 24.2.2025.

#End 16:00

Chat:
01:01:08

Chat

4
Personen

Heben

Reagieren

Ansicht

Weitere

Kamera

Mikro

Teilen beenden

Verlassen

Daniel Klotz

Laszlo Bukai

Tejada, Alberto (Nicht überprüft)

Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft)
Besprechungschat

Einige Personen in diesem Chat befinden sich außerhalb Ihrer Organisation. Es ist möglich, dass sie nachrichtenbezogene Richtlinien haben, die für den Chat gelten.Weitere Informationen

Daniel Klotz wurde zu der Besprechung eingeladen.
Daniel Klotz wurde zu der Besprechung eingeladen.
Tekieli Lukasz, JC-60 (Nicht überprüft) wurde zu der Besprechung eingeladen.
Tekieli Lukasz, JC-60 (Nicht überprüft) wurde zu der Besprechung eingeladen.
Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) wurde zu der Besprechung eingeladen.
Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) wurde zu der Besprechung eingeladen.
Link https://github.com/eclipse-score/score... x Tekieli Lukasz, JC-60 (Nicht überprüft)
Tekieli Lukasz, JC-60 (Nicht überprüft)
15:09

#167

I need to drop. x Bjedov Dragan, JC-12 (Nicht überprüft)
Bjedov Dragan, JC-12 (Nicht überprüft) (Extern)
15:30

I need to drop.

This is the link to the Contribution Reques... x Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft)
Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft) (Extern)
15:34

This is the link to the Contribution Request.

https://eclipse-score.github.io/score/main/process/guidance/contribution_request/index.html

There is a subsection for the Feature Request Template.

https://eclipse-score.github.io/score/main/process/guidance/contribution_request/templates/feature_request_template.html

👍
2 Gefällt mir-Reaktionen.
2
Krivoborodov Anton, JC-1 Bjedov Dra... x Tekieli Lukasz, JC-60 (Nicht überprüft)
Tekieli Lukasz, JC-60 (Nicht überprüft)
15:55

Krivoborodov Anton, JC-1 Bjedov Dragan, JC-12 for next week sync we need to bring the justification why ITF was chosen over other alternatives

Not sure, but will this include also, which... x Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft)
Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft) (Extern)
15:56

Not sure, but will this include also, which other solutions were considered?

Referenz beginnen, Not sure, but will this ... x Tekieli Lukasz, JC-60 (Nicht überprüft)
Tekieli Lukasz, JC-60 (Nicht überprüft)
15:56

Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft)
19.02.2025 15:56
Not sure, but will this include also, which other solutions were considered?
Yes it will.

👍
2 Gefällt mir-Reaktionen.
2
Atm-Acn x Tejada, Alberto (Nicht überprüft)
Tejada, Alberto (Nicht überprüft) (Extern)
15:56

Atm-Acn

Link https://github.com/orgs/eclipse-score/... x Tekieli Lukasz, JC-60 (Nicht überprüft)
Tekieli Lukasz, JC-60 (Nicht überprüft)
15:57

Integration testing (view)

I need to drop. Talk tou latest next week. x Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft)
Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft) (Extern)
15:57

I need to drop. Talk tou latest next week.

Need to drop, thank you. x Tekieli Lukasz, JC-60 (Nicht überprüft)
Tekieli Lukasz, JC-60 (Nicht überprüft)
15:59

Need to drop, thank you.

hat Kontextmenü

0 replies

dneail1601 · 2025-02-26T14:15:06Z

dneail1601
Feb 26, 2025
Collaborator Author

Meeting minutes 26.02.2025

Participants:
Lars Bauhofer
AlbertoLAzlo
Philipp left 16:01
Rebecca joined 15:20

#Start time: 15:05

Remaining topics:

Formulate plan according to https://github.com/orgs/eclipse-score/projects/4, github.com/orgs/eclipse-score/projects/5 -> @dneail1601
Demonstrator for test generator
ITF needs to be made available -> Dragan (open TBD, possible end May)
Setup/use for virtual environment

-Specific Roadmap is required (proposal in discussion) -> Available in Qorix pubilc space (TBD add link)
Start with inductive (code based) and later align with requirements and architecture (based on sphinx needs) (deductive)

-Distribution and contribution shall be organized -> Project plan
Carry over from the former project. It is expected that functionalities work together so the inductive approach provides the input for the score incubation setup. See chat for pytest(ITF) integration. First run and example would be with sphinx needs and pytest but after a working demonstrator the discussion for an open and exchangeable interface shall be introduced from that experience. Avoid to tight coupling in the future. Open approach.

Roadmap (Rebecca):

Bring the minor tasks according the new milestones. Update the plantuml gantt chart and provide it in S-Core. Put it in the verification plan.
- update milestones
- add detailed sub tasks

Philipp will introduce a meeting for findings from the predecessor project. (Sent invitation Fri 10:30)

Milestones:
In general the automatic generation of test and impl. Sphinx elements shall work stable before the requirements and architecture arrive. Create a pull request for that and a feature request.

One for the roadmap
One for functionality (proposal: https://github.com/qorix-group/Score-Testing/blob/main/Proposal/General_Concept/doc/General_Concept.rst)
Must be ready by monday. Check today.

Future topics:

Get the Base code interpreter running with C++ and RUST
Roadmap
Milestone 1.4.2025 reachable? (Automatic tests PLUS Manual tests available)

#End time 16:15

Chat:
01:14:35

Chat

2
Personen

Heben

Reagieren

Ansicht

Weitere

Kamera

Mikro

Teilen beenden

Verlassen

Tejada, Alberto (Nicht überprüft)

Besprechungschat

Einige Personen in diesem Chat befinden sich außerhalb Ihrer Organisation. Es ist möglich, dass sie nachrichtenbezogene Richtlinien haben, die für den Chat gelten.Weitere Informationen

Daniel Klotz wurde zu der Besprechung eingeladen.
Daniel Klotz wurde zu der Besprechung eingeladen.
I have a few tickets, I want to address: Li... x Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft)
Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft) (Extern)
15:08

I have a few tickets, I want to address:

#320

Which lead into #441

Which also relates to sub issues:

#497

#498

#499

Milestones for the planning of this year: ... x Lars Bauhofer
Lars Bauhofer
15:09

Milestones for the planning of this year: Milestone Planning

https://github.com/orgs/eclipse-score/discussions/434

In detail we need to have some discussion a... x Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft)
Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft) (Extern)
15:11

In detail we need to have some discussion about the methods and rigour where they get applied with an argument: https://eclipse-score.github.io/score/pr-441/platform_management_plan/software_verification.html#methods

Link https://github.com/qorix-group/Score-T... x Daniel Klotz
15:15
Daniel Klotz

https://github.com/qorix-group/Score-Testing/blob/main/Proposal/General_Concept/doc/General_Concept.rst

Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) wurde zu der Besprechung eingeladen.
Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) wurde zu der Besprechung eingeladen.
Here is an example from sphinx in test case... x Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft)
Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft) (Extern)
15:22

Here is an example from sphinx in test case description: https://github.com/PhilipPartsch/ReConf2023-Product-As-Code/blob/main/tests/merge_dicts_test.py

Referenz beginnen, Milestones for the plann... x Lars Bauhofer
Lars Bauhofer
15:27

Lars Bauhofer
26.02.2025 15:09
Milestones for the planning of this year: Milestone Planning https://github.com/orgs/eclipse-score/discussions/434
will need to drop out now, Daniel Klotz can you please start the breakdown of the issues for the testing community according to the above milestone plan. This is required within the next few weeks in order to evaluate whether we can commit milestone dates or if we would need to replan on that level.

Link https://github.com/orgs/eclipse-score/... x Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft)
Ahmann Philipp (ETAS/XBC-PCN) (Nicht überprüft) (Extern)
15:41

Milestone Planning

https://github.com/orgs/eclipse-score/discussions/434

Link https://github.com/qorix-group/Score-T... x Daniel Klotz
15:42
Daniel Klotz

https://github.com/qorix-group/Score-Testing/blob/main/Proposal/Project/Project_Plan.puml

hat Kontextmenü

Laszlo Bukai hat den Anruf verlassen

0 replies

dneail1601 · 2025-03-05T14:00:19Z

dneail1601
Mar 5, 2025
Collaborator Author

Meeting minutes 05.03.2025

Participants:
Philipp Ahmann
Julian Schneider
Alberto
LAzlo
Lukasz
Johannes Glamsch
Dragan

#Start time: 15:05

Remaining topics:

Milestones Test Generator available: 30.03.2025 after that incorporation of Requirements are avaialble

Get to Tool/Generator running based on tree-sitter library 30.3.
Synchonize with the Requirements 1.4.
2.1 Adapt to ITF
Tool verification 1.5.

ITF with SSH, DLT at mid April. (S-Core)

Setup/use for virtual environment (1. Pure virtual environment (ITF) 2. Hardware based deviation 3. End target) S-Core main focus is without hardware-system aspects of testing.

C++ and Rust dll gnerated and test generation is currently developed and tested

-Distribution and contribution shall be organized -> Project plan
Carry over from the former project. It is expected that functionalities work together so the inductive approach provides the input for the score incubation setup. See chat for pytest(ITF) integration. First run and example would be with sphinx needs and pytest but after a working demonstrator the discussion for an open and exchangeable interface shall be introduced from that experience. Avoid to tight coupling in the future. Open approach.

Roadmap (Rebecca):

see milestones above

Milestones:
In general the automatic generation of test and impl. Sphinx elements shall work stable before the requirements and architecture arrive. Create a pull request for that and a feature request.

One for the roadmap

Roadmap: internal testing acceptable -> Group testing -> S-Core availability
One for functionality (proposal: https://github.com/qorix-group/Score-Testing/blob/main/Proposal/General_Concept/doc/General_Concept.rst)

Future topics:
Get the Base code interpreter running with C++ and RUST -> Interpreter lib ready
Provide the test generator for the team for individual examination, put in the Qorix Proposal Github folder when internal tests are finished
How to introduce explorative and intuitive testing

Chat:

Daniel Klotz wurde zu der Besprechung eingeladen.

I have a few tickets, I want to address:
#320
Which lead into #441
Which also relates to sub issues:
#497
#498
#499

Improvement: Document Verification Process · Issue #320 · eclipse-score/score
ImportantMake sure to link this issue with the PR for your improvement. Document in score repository (until the process_description repo is available) migrate verification parts from incubator to s...

Milestones for the planning of this year: Milestone Planning
https://github.com/orgs/eclipse-score/discussions/434
Milestone Planning

In detail we need to have some discussion about the methods and rigour where they get applied with an argument: https://eclipse-score.github.io/score/pr-441/platform_management_plan/software_verification.html#methods
Software verification — Score 0.1 documentation

https://github.com/qorix-group/Score-Testing/blob/main/Proposal/General_Concept/doc/General_Concept.rst

Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) wurde zu der Besprechung eingeladen.

Here is an example from sphinx in test case description: https://github.com/PhilipPartsch/ReConf2023-Product-As-Code/blob/main/tests/merge_dicts_test.py
ReConf2023-Product-As-Code/tests/merge_dicts_test.py at main · PhilipPartsch/ReConf2023-Product-As-Code
Contribute to PhilipPartsch/ReConf2023-Product-As-Code development by creating an account on GitHub.

Lars Bauhofer
Milestones for the planning of this year: Milestone Planning https://github.com/orgs/eclipse-score/discussions/434
will need to drop out now, Daniel Klotz can you please start the breakdown of the issues for the testing community according to the above milestone plan. This is required within the next few weeks in order to evaluate whether we can commit milestone dates or if we would need to replan on that level.

Milestone Planning
https://github.com/orgs/eclipse-score/discussions/434
Milestone Planning • eclipse-score
Milestone Planning

https://github.com/qorix-group/Score-Testing/blob/main/Proposal/Project/Project_Plan.puml

Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) hat den Chat verlassen.

Mittwoch 16:15 Besprechung beendet: 1Std. 14Min. 56Sek.

0 replies

dneail1601 · 2025-03-12T13:42:49Z

dneail1601
Mar 12, 2025
Collaborator Author

Meeting minutes 12.03.2025

Participants:
Alberto
Lazlo
Dragan
Daniel
Julian

#Start time: 15:05

Topics:

Compiler environment
llvm compiler is set. Test environment will use llvm for the first demonstrator.
Task setup (epic etc.)
Organisation is as follows:
Top level is epic will have the latest milestone of its sub elements (one)
Sub levels are tasks or sub projects with one milestone each.
Sub levels can be CFT (cross functional or for one team)
Status ITF
Logging and SSH by ending of April.
Rest of functionality can not be estimated. Multiple months. -> Tests will be on generic pytest until ITF availability.
Status Test generation
Example was shown. Tasks will be generated in the structure outlined above (Tech lead agreement 10.3.2025). Test team will volunteer for tasks. Open tasks will be distributed in the weekly meeting and tracked there. Upcoming tasks will be standard confirmation of the testing apprach (completeness, correctness etc.). Llvm version 20.1 was used for Cpp code interpretation. One or two more days are required for review and further testing and then the available code will be shared. First as discussion then next meeting transfer to github after discussion.

Future upcoming topics (team):
- Task distribution
- Tool execution (automation CT) zuul, Jenkins etc.
- Configuration for Tool with JSON
- Test vector generation (virtual environment)
Chat:
brb

Sorry, I cannot join today. Greetings from embedded world!

Zuul

#End meeting 15:45

0 replies

dneail1601 · 2025-03-19T13:58:39Z

dneail1601
Mar 19, 2025
Collaborator Author

Meeting minutes 19.03.2025

Participants:
Lazlo
Philipp
Dragan
Alberto

#Start time: 15:03

Topics:

Parser proposal:
https://github.com/qorix-group/Score-Testing/blob/main/Proposal/main.py

See the chat for already available python interpreter script.

Audit outcome:
Link to the outcome provided from Philipp.

ITF Testing on SW. ITF currently runs only on target. Single C++ can not run in the current configuration.
Dragan: Unit tests run in G-Test (Google). The DUT-SW has to be turned into a compiled binary that is deployed to an ECU target environment (can be yirtual). -> ITF is therefore linked to a target execution and the test can not run alone in a local environment. Basically a full integration is running (big bang).

-> urgent task is to get a running example of a test execution on an virtual environment (usable by everybody)
-> There is an example in ITF on S-Core without much documentation. Documentation needs to be created new.

Prioritization ITF migration
-> Which parts need to be available next and at which time. List and content to be provided by Dragan.

Auto documentation has to be determined (doc strings in code etc.)

Future upcoming topics (team):
    Work on the audit findings and comments -> proposal 
    Task distribution
    Tool execution (automation CT) zuul, Jenkins etc.
    Test vector generation (virtual environment)

Chat:
https://eclipse-score.github.io/score/main/_images/score_traceability_model_wp_overview.drawio.svg

This shows the traceability concept,, the anticipated test levels and their reports.
The code generation could fit into the field of unit level testing.

These were fields that BMW proposed for test specification: https://eclipse-score.github.io/score/main/process/process_areas/verification/guidance/verification_specification.html
Also here is the mentioning of Test properties: https://eclipse-score.github.io/score/main/process/process_areas/verification/guidance/verification_process_toolreqs.html
The "specification" should be as part of the test implementation.
Test Specification Guideline — Score 0.1 documentation

https://github.com/PhilipPartsch/score_inc_process_test_management/blob/PhilipPartsch_testing_in_sphinx/tests/test_your_product.py
score_inc_process_test_management/tests/test_your_product.py at PhilipPartsch_testing_in_sphinx · PhilipPartsch/score_inc_process_test_management
Incubation repository for Process - Sphinx-Test management - PhilipPartsch/score_inc_process_test_management

#724
Bugfix: Findings on verification process during interim audit 3 · Issue #724 · eclipse-score/score
ImportantMake sure to link this issue with the PR for your bugfix. Check the unit test workflow add dynamic code analysis to the verification methods control flow analysis not on L1 but on L2/L3 te...

https://labgrid.readthedocs.io/en/latest/
Welcome to labgrid’s documentation! — labgrid 24.1.dev198 documentation

https://github.com/labgrid-project/labgrid
GitHub - labgrid-project/labgrid: Embedded systems control library for development, testing and installation
Embedded systems control library for development, testing and installation - labgrid-project/labgrid

ITF Readme: https://github.com/eclipse-score/itf/blob/main/README.md
itf/README.md at main · eclipse-score/itf
Integration Testing Framework repository. Contribute to eclipse-score/itf development by creating an account on GitHub.

Milestone Planning (view)
Milestone Planning • eclipse-score
Milestone Planning

#End meeting 16:00

8000

0 replies

dneail1601 · 2025-03-26T14:01:26Z

dneail1601
Mar 26, 2025
Collaborator Author

Meeting minutes 26.03.2025

Participants:

Julian Schneider
Rebecca Markert
Lars Bauhofer
Lazlo
Alberto
Philipp Ahmann

#Start time: 15:03

Topics:

Planning -> Invite to a general test planning meeting (Monday)
Audit outcome (L1-L3 re-adjustment, fault injection)

Decision:

Email to Dragan about progress. Since he is absent today.
Create Sub tasks for upcoming milestone:
- One Epic for Test execution
- Sub Task BMW Test carry over (making runable, incl. ITF)
- Sub Task LoLa Test (Ulrich Huber refering)
- Sub Task for Lib internal fault injection (data flow analysis)
- Open question is also the coverage from already existing tests (BMW)
Refine the test strategy:
1. Get the Unit Tests and existing tests running (Milestone) (g-Test)
2. Combine Unit Tests to module/SW-Integration tests (g-Test)
3. Check coverage and completeness
4. Develop new tests
5. L3 (Target) comparison (virtual versa ITF)
6. Integration into CI/CT
7. Automate test generation
Main focus shall be on creating running demonstrators.
People attendance regarding the meeting. Decision need to be made. Close communication with BMW as main supplier is required. -> email
- Content what will be provided and where additional work would be required
- Timeline Milestones for ITF release required (time and functionality)
Second test execution framework shall be considered for dual source and cross check of ITF (Proposal for next week to create a decision matrix)

Audit findings:

Bugfix: Findings on verification process during interim audit 3 #724

Comments to be added here:

process: adjust test levels and methods #792 process: adjust test levels and methods #792

Chat:

None

#End meeting 16:00

0 replies

dneail1601 · 2025-04-02T12:50:32Z

dneail1601
Apr 2, 2025
Collaborator Author

Meeting minutes 02.04.2025

Participants:

Julian Schneider (left 14:30)
Alberto
Philipp Ahmann
Dragan
dk1601

#Start time: 15:04

Topics:

ITF Roadmap
Additional Frame (decision)
Software Integration Tests with G-Test (decision)
IPC is test focus for 0.5 release

Discussion:

Roadmap ITF:
No update available right now. Anton was not reachable. No DLT Sending in 0.5. Logging will only be for console output.
Update when internal BMW coordination was taking place. Re schedule 09.04.2025. Required is function to time relation regarding ITF.
Scope Framework for platform test. BMW also has some Robot Framework tests. Question: Are already existing packages usable for our context?
SW Integration Tests with G-Test:
Presentation made. Example will be uploaded on the proposal area and link will be added here. Presented for C++. Rust will be done later, but it is expected to work the same way. Goal is parallel Test/Source integration and switching execution during runtime.
https://github.com/qorix-group/Score-Testing/blob/main/Proposal/Proxy%20Test.PNG
https://github.com/qorix-group/Score-Testing/blob/main/Proposal/Proxy%20Tests%20with%20GTest.cpp
IPC will be main focus since inter lib/feature tests will rely on ITF communication manipulation. This will be fixed in the test strategy. If anyone deviates from that process this entity will be responsible of describing the process (will not be part of S-Core e.g. direct register access of processor).

Decision:

Robot Framework will be used for Platform tests. Tasks will be added accordingly.
SW Intergration will be linked here
Tasks will be created according to this setting and test strategy.
Working, real example for IPC for release 0.5 on all test levels (Unit, Integration, Platform). Ideal 100% coverage.
Robot Framework Task -> Philipp
SW Integration with G-Test according to example -> Alberto
Unit tests IPC -> Ulrich Huber (to be contacted)
Proxy example Rust -> Daniel

Future Topics:

Rust example for SW Ingratiation test with Unit Framework realizing the proxy attempt.

#End time: 15:49

Chat:

I will join in about 3 minutes. by Ahmann Philipp (ETAS/XBC-PCN)
Ahmann Philipp (ETAS/XBC-PCN) (External)
3:02 PM

I will join in about 3 minutes.

0 replies

dneail1601 · 2025-04-09T12:57:19Z

dneail1601
Apr 9, 2025
Collaborator Author

Meeting minutes 09.04.2025

Participants:
Philipp Ahmann
Lazlo
Rebecca
dk1601

#Start time: 14:04 (CET)

Discussion:

ITF Roadmap -> Meeting Anton Fr. 11.04.
Feature Tests
Robot Framework for Platform tests
Will be added as a feature with separate fork. -> Approval from Archi team.
First run will be as a cross-reference on feature level to the new feature tests (Proxy approach).
create separate meeting with Ulrich Huber for IPC Unit tests. email -> Daniel
Check for SDD for IPC. -> Goal to have working examples for 0.5 -> Proof of concept
Create "dummy SDD" for linking simulation
Epics are still not created (but will be done soon)
email Alberto regarding the feature implementation
Also add Lazlo to working group (below 50% availability)
Question to be answered, shall be handled in a combined topic. -> New Discussion with links to all relevant Q&A

Decision:

One Epic for the RF (Robot Framework) -> Limited to milestone 19.04.
One Epic for the Feature Tests -> Limited to milestone 19.04.
One Epic for test execution and CI/CT (continuous integration/continuous testing)

Future Topics:

Get the implementations for feature test running, get platform tests running, get unit tests running. Expected milestone: 19.04.
Could we use RF for management of CT and automated build configuration (Test focus, Impact analysis mitigation etc.) -> Philipp
Proxy approach for Rust (template implementation)

#End meeting: 14:55 (CET)

Chat:
I need to leave. Thanks.

Markert Rebecca (ETAS/XBC-PCS) (Unverified) left the chat.

0 replies

dneail1601 · 2025-04-16T12:45:36Z

dneail1601
Apr 16, 2025
Collaborator Author

Meeting minutes 16.04.2025

Participants:
Alberto
Lazlo
Dragan
dk1601

#Start time: 14:04 (CET)

Discussion:

ITF Roadmap -> Discussed on Friday -> provided this month
Feature for proxy approach -> Feature request to be done since concept should work with RUST as well (template will be made available in Proposal area)
Rust example for proxy approach available
Will be discussed in the feature request especially with the aspect of adaptive autosar or fixed libs or binaries.
Implementation examples required for performance, persistence, IPC (lola)
performance -> Lazlo (POC, full test is not required, focus on C++)
persistence -> Lazlo (POC, full test is not required, focus on C++))
IPC -> Alberto ( 2-3 POC examples, focus on C++))
-> Test artifacts -> Traceability (Requirements/SDD)?

Persistency will be pilot module for full implementation, requirements, Designs, Architecture and traceability.
New appointment for meeting
Please check @ALL for availablity on thursday afternoon -> try to incite a vote on that
Integration proxy model for C++ code
Question: Support for implementation requested. Problem with dependencies. -> Create a workshop for implementation aspects -> Thursday before 2 p.m. (CET) or after 3 p.m. -> 1600 or 1700 (1 hour workshop)

Decision:

New meeting time proposal for Thursday
Workshop for proxy model

Future Topics:

traceability, SDD, safety analysis -> Audit preparation
Platform tests & example

#End meeting: 14:45 (CET)

Chat:

empty

0 replies

dneail1601 · 2025-04-23T12:25:25Z

dneail1601
Apr 23, 2025
Collaborator Author

Meeting minutes 23.04.2025:

Lazlo
Alberto
Daniel

#Start time: 15:04 (CET)

Discussion:

Question for building containers -> Anton
Discussion of the current state for persistency, performance and IPC. -> Currently no working examples are ready by now. Update next week.
Time problems with other deadline for Alberto -> Support reqired -> If IPC Code is available get a running example in parallel -> Daniel

Decision:

None, keep working on the POC examples

Future Topics:

CI/CT integration

#End meeting: 15:30

Chat:
#970
Task: Implement POC and Example for persistency · Issue #970 · eclipse-score/score
Tests with the proxy approach to show integration and feature test POC for persitency feature.

0 replies

dneail1601 · 2025-04-30T12:48:05Z

dneail1601
Apr 30, 2025
Collaborator Author

Meeting minutes 30.04.2025:

Lazlo -> dropped 14:30
Alberto
Daniel
Pjotr
Igor
Dragan
Julian -> dropped 14:30
Philipp

#Start time: 15:04 (CET)

Discussion:

Question for building containers -> Anton
ITF project plan
- Epics added to score roadmap -> Dates need to be added
- Planning contains the estimated content for 2025
Progress With IPC
- Code available locally, Proxys in implementation, First topic is to create POC, lot of content -> later support by Pjotr, Sources compilable and runnable, Test implementation will follow
Progress with persistency
- Sources compilable and runnable, Test implementation will follow, starting next week -> Probably not reachable by 8.5.2025
Test strategy incorporation
- Issues will be created (daniel) and assign it to Philipp
Platform testing
- Robot Framework (RF) still in planning phase, not much time to work on it. No time for Philipp until mid may.
  Epic: (Initial) Robot Framefork for (Feature &) Platform testing #878 doubles Epic: Establish Robot Framework for Platform tests #966 -> Delete Epic: Establish Robot Framework for Platform tests #966
- Dragan opposes the use of robot framework as arbitrator
- Volunteer required for supporting Philipp -> we'll wait for availability of Philipp
CFT -> asked for proxy approach adaption for unit tests, currently in discussion

Decision:

Test Strategy to be added as issue
RF to be delaed slightly
POC for Feature tests in making support -> daniel

Future Topics:

CI/CT integration
Get POC operational by end 05.2025
Get 100% coverage by 08.2025
IPC is considered to have major changes to the IPC repo

#End meeting: 15:47

Chat:
S-CORE Roadmap (view)
S-CORE Roadmap • eclipse-score
S-CORE Roadmap

#878
Epic: (Initial) Robot Framefork for Feature & Platform testing · Issue #878 · eclipse-score/score
Evaluate usage of Robot framework for test case description and execution. https://robotframework.org/ ITF today already can interact with Robot framework. See if/how it integrates with bazel and g...

I have to leave for a another meeting.

0 replies

dneail1601 · 2025-05-07T12:30:46Z

dneail1601
May 7, 2025
Collaborator Author

Meeting minutes 07.052025:

Participants:
Daniel
Pjotr
Igor

Excused absent:
Lazlo -> Parallel meeting
Philipp -> Workshop

#Start time: 15:04 (CET)

Discussion:

Feature Request added
Issue for Feature test to be added
Dates for ITF release still missing
Rust tutorial added for proxy appraoch -> see chat
Message from Lazlo -> see Chat
Question: Shall a pull request permitted with higher test levels (feature, platform) failing -> Must a final pull produce all tests "green" -> Daniel (Tech lead circle)

Decision:

Working on POC continues

#End meeting: 15:30

Chat:

I'm not able to join due paralel meeting.
I am still working on the performance modul.

https://github.com/qorix-group/Score-Testing/blob/main/Proposal/Rust%20Proxy%20Testing%20Tutorial.rst
Score-Testing/Proposal/Rust Proxy Testing Tutorial.rst at main · qorix-group/Score-Testing
Summary of testing related topics (Proposal, Solutions etc.) - qorix-group/Score-Testing

0 replies

dneail1601 · 2025-05-14T13:02:30Z

dneail1601
May 14, 2025
Collaborator Author

Meeting minutes 14.052025:

Participants:
Daniel
Pjotr
Igor
Lazlo
Albertó
Dragan
Anton
Rebecca

Excused absent:
Philipp -> Congress

#Start time: 15:04 (CET)

Discussion:

POC C++ file
POC Rust
Progress with POC on Lola, Persitency, Performance
Tracking of progress to be done offline -> Separate issue
Dates for ITF release have been added
Question:
How to handle binaries which are within one lib -> granularity
Since IPC is the only communication interface the approach is still valid. Problem arises when other communication paths than IPC are used between two binaries.
IPC (lola) (Alberto)
- Try to build executable -> compilation possible
- https://github.com/eclipse-score/communication/tree/main#
- Problems with dependencies and building platform
- No tests implemented yet -> starting with new repo
- Next week demonstration -> Appointment for review TBD after that
Persistency (Lazlo, Igor, Piotr)
- See lola comments
- Next week demonstration -> Appointment for review TBD after that
- Piotr, Igor work simultaniously
Performance (Piotr, Igor)
- Still learning
Big picture required for test integration in respect to platform / feature integration
Goal for End of may to find design flaws and showstoppers of the approach which invalidates the approach. From that on the whole thing shall be "rinse and repeat".
Separate meeting for Approach in Rust for the proxy model in data flow analysis, control flow analysis -> Probably Friday

Decision:

Fokus on POC on real code
Find flaws

Future point:

Integrate and run the tests within the ITF and possibly on a target

#End meeting: 16:01

Chat:
Hi!

https://github.com/eclipse-score/communication/tree/main#
GitHub - eclipse-score/communication: Repository for the communication module LoLa
Repository for the communication module LoLa. Contribute to eclipse-score/communication development by creating an account on GitHub.

sorry, need to drop to a parallel meeting

Need to leave for another meeting. Thanks!

Markert Rebecca (ETAS/XBC-PCS) (Nicht überprüft) hat den Chat verlassen.

ntd. Thanks

0 replies

dneail1601 · 2025-05-21T12:55:13Z

dneail1601
May 21, 2025
Collaborator Author

Meeting minutes 21.052025:

Participants:
Daniel
Pjotr
Igor
Lazlo
Albertó

#Start time: 14:02 (CET)

Discussion:

POC
- Persistency (KVS)
  - Currently not running with Lazlo
  - Currently not running with Daniel
    -> Synchronisation required -> After that the proposal will be released (Proxy model), wait here for the mocking results
- Lola (IPC)
  - Still working on the integration test. High workload prevents progress here.
  - Test cases developed but not running
- inc_orchestrator -> Lazlo
Proxy Model vs Mocking mechanism (effort)
- Pro Mocking: Lazlo, Alberto, Piotr, Igor ->(standard feature of GTest)
- Contra Mocking: None
Requirements and Designs (including Software Detailed Design) will be available by end of the month for Persistency -> linkage, traceability, coverage (That is planned)
Problems with the proxy model encountered:
- Nested members and member functions
- Fault injection on proxy level
- Maintainability -> becomes too complex with bigger features
Advice: Use some AI Model to create Frameworks

Decission:

Create an POC example for Persistency with Mocking -> Daniel -> Proposal (maybe Friday) -> Review by Piotr&Lazlo

Future Topics:

How to integrate with platform tests and Robot Framework, plus ITF, to have test artifacts here for virtual and target environment

#End meeting: 15:55

Chat:

0 replies

Eclipse S-CORE

Meeting Minutes #249

Uh oh!

dneail1601 Jan 29, 2025 Collaborator

Replies: 18 comments · 2 replies

Uh oh!

Uh oh!

dneail1601 Jan 29, 2025 Collaborator Author

Uh oh!

Uh oh!

dneail1601 Feb 5, 2025 Collaborator Author

Uh oh!

dneail1601 Feb 5, 2025 Collaborator Author

Uh oh!

julian711 Feb 6, 2025 Collaborator

Uh oh!

pahmann Feb 12, 2025 Collaborator

Uh oh!

dneail1601 Feb 12, 2025 Collaborator Author

Uh oh!

dneail1601 Feb 19, 2025 Collaborator Author

Uh oh!

dneail1601 Feb 26, 2025 Collaborator Author

Uh oh!

dneail1601 Mar 5, 2025 Collaborator Author

Uh oh!

dneail1601 Mar 12, 2025 Collaborator Author

Uh oh!

dneail1601 Mar 19, 2025 Collaborator Author

Uh oh!

Uh oh!

dneail1601 Mar 26, 2025 Collaborator Author

Uh oh!

Uh oh!

dneail1601 Apr 2, 2025 Collaborator Author

Uh oh!

Uh oh!

dneail1601 Apr 9, 2025 Collaborator Author

Uh oh!

dneail1601 Apr 16, 2025 Collaborator Author

Uh oh!

dneail1601 Apr 23, 2025 Collaborator Author

Uh oh!

dneail1601 Apr 30, 2025 Collaborator Author

Uh oh!

dneail1601 May 7, 2025 Collaborator Author

Uh oh!

Uh oh!

dneail1601 May 14, 2025 Collaborator Author

Uh oh!

dneail1601 May 21, 2025 Collaborator Author

dneail1601
Jan 29, 2025
Collaborator

Replies: 18 comments 2 replies

dneail1601
Jan 29, 2025
Collaborator Author

dneail1601
Feb 5, 2025
Collaborator Author

dneail1601 Feb 5, 2025
Collaborator Author

julian711 Feb 6, 2025
Collaborator

pahmann
Feb 12, 2025
Collaborator

dneail1601
Feb 12, 2025
Collaborator Author

dneail1601
Feb 19, 2025
Collaborator Author

dneail1601
Feb 26, 2025
Collaborator Author

dneail1601
Mar 5, 2025
Collaborator Author

dneail1601
Mar 12, 2025
Collaborator Author

dneail1601
Mar 19, 2025
Collaborator Author

dneail1601
Mar 26, 2025
Collaborator Author

dneail1601
Apr 2, 2025
Collaborator Author

dneail1601
Apr 9, 2025
Collaborator Author

dneail1601
Apr 16, 2025
Collaborator Author

dneail1601
Apr 23, 2025
Collaborator Author

dneail1601
Apr 30, 2025
Collaborator Author

dneail1601
May 7, 2025
Collaborator Author

dneail1601
May 14, 2025
Collaborator Author

dneail1601
May 21, 2025
Collaborator Author