LOBSTER
The Lightweight Open BMW Software Traceability Evidence Report allows you to demonstrate software traceability and requirements coverage, which is essential for meeting standards such as ISO 26262.
This package contains a tool extract tracing tags from ISO C++ test code. The tracing tags are identified by searching for configurable markers in the comments above the test code.
Tools
This LOBSTER package contains only one tool, lobster-cpptest.
It can be used to extract references from C++ tests.
The most frequent use case is that, the references point to requirements.
But lobstser-cpptest is agnostic to that, and the references can point to any kind
of artefact.
The references must be given inside a comment above the test case itself.
The resulting *.lobster file will then contain a LOBSTER item per test case.
This file can be used to generate a LOBSTER report.
Configuration
The tool requires a YAML configuration file to define its settings. You must provide this file when running the tool to specify parameters to process.
Usage
This tool supports C++ code.
For this your C++ tests must have a documentation with markers:
The tool supports just @requirement marker.
Here is an example:
/**
* @requirement CB-#1111, CB-#2222,
* CB-#3333
* @requirement CB-#4444 CB-#5555
* CB-#6666
*/
TEST(RequirementTagTest1, RequirementsAsMultipleComments) {
// your test implementation here
}
You can also provide parameters to specify the configuration of the tool (output_file, codebeamer_url, kind, and files).
Examples:
output: 'component_tests.lobster'
kind: 'req'
codebeamer_url: "https://codebeamer.com"
You can also include CPP files in the YAML configuration file.
files:
- 'path/to/source1.cpp'
- 'path/to/source2.cpp'
Note: File paths are accepted only in single quotes.
Technical Aspects
lobster-cpptest now displays a test-name instead of a fixture-name
in the lobster-report and lobster-html-report.
Known Issues
Please refer to lobster-cpptest documentation for a full list of known issues.
Copyright & License information
The copyright holder of LOBSTER is the Bayerische Motoren Werke Aktiengesellschaft (BMW AG), and LOBSTER is published under the GNU Affero General Public License, Version 3.
Release files for bmw-lobster-tool-cpptest 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bmw_lobster_tool_cpptest-1.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Release files / bmw_lobster_tool_cpptest-1.0.6-py3-none-any.whl
| Download URL | bmw_lobster_tool_cpptest-1.0.6-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
435a282555afe63bc09d3849bf8713b43d2124bcaac307beae1e3a0287e677e9
|
|
BLAKE2b-256 checksum How to use checksums |
7725347628866b68f3b8b85951f30d2bc7f9dd7c2eb57a6dade3386b8fcd336f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logSecurity for bmw-lobster-tool-cpptest 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for bmw_lobster_tool_cpptest-1.0.6-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
