Skip to content

Conversation

@pahmann
Copy link
Member

@pahmann pahmann commented Feb 21, 2025

This is the porting of the work done in the incubator project.

It includes the following artifacts, adopted to the latest syntax and checks for S-Core:

  • Guidance
  • Work Products
  • Report template
  • Requirement to test linking
  • Test case templates
  • S-Core verification plan draft

Implements: #320

Also-by: @julian711, @aschemmel-tech , @hoe-jo

This is the porting of the work done in the incubator project. It includes the following artefacts, adopted to the latest syntax and checks for S-Core:

- Guidance
- Work Products
- Report template
- Requirement to test linking
- Test case templates
- S-Core verification plan draft

Implements: #320

Also-by: @julian711
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
Implements: #320
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
@github-actions
Copy link

The created documentation from the pull request is available at: docu-html

@masc2023 masc2023 added this to the SCORE Process Audit 3 milestone Feb 23, 2025
=====================

This guideline outlines the responsibilities and procedures for developers performing verification activities (test
case creation, inspection, and review) for S-Core documentation, Rust and C/C++ projects of the platform.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • should we leave out name "S-Core"?
  • documentation + tooling? We also need some guidance to link our tools to process requirements for Tool Qualification

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

process requirements are still missing

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

last part of process requirements added to issue #623

- valid | invalid
-
-
* - TestType
Copy link
Contributor

@hoe-jo hoe-jo Feb 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provide more examples including description

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test type descriptions like for boundary analysis is a topic which will be discussed within testing community (and documented in process).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added this finding to issue #623

Copy link
Contributor

@aschemmel-tech aschemmel-tech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see inline comments, first iteration

Implements: #320
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
@pahmann
Copy link
Member Author

pahmann commented Feb 25, 2025

@hoe-jo this commit in #441 is for you: workproducts: update verification and requirements

I removed some duplicated items and added the requirements inspection to your work products, as you already have the template for it.

Implements: #320
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
Implements: #320
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
@pahmann pahmann force-pushed the pahmann_verification_incubator branch from 0d24a0a to e40ca7b Compare February 25, 2025 16:10
Implements: #320
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
@masc2023 masc2023 linked an issue Mar 10, 2025 that may be closed by this pull request
Implements: #320
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added 3 commits March 10, 2025 11:10
Implements: #320
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
Implements: #320
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
Implements: #320
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
@pahmann
Copy link
Member Author

pahmann commented Mar 10, 2025

@aschemmel-tech kindly do a review on the current state. I should have addressed all your pending concerns.

Missing part for final commit on this PR will be the transfer of TODOs into improvement issue(s).

@pahmann pahmann requested a review from aschemmel-tech March 10, 2025 14:11
pahmann added 3 commits March 10, 2025 15:07
Implements: #320
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
- created issue number is #623

Implements: #320
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
@pahmann
Copy link
Member Author

pahmann commented Mar 10, 2025

@aschemmel-tech, from my perspective we are ready to merge. 🎉

Copy link
Contributor

@aschemmel-tech aschemmel-tech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, let's merge

@aschemmel-tech aschemmel-tech merged commit a8f8c84 into main Mar 10, 2025
10 checks passed
@aschemmel-tech aschemmel-tech deleted the pahmann_verification_incubator branch March 10, 2025 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Epic: (Initial) Processes Verification

6 participants