bmw-software-engineering / lobster Goto Github PK

the name synthesis doesn't deal well with paths like C:\potato\foo.json

Replace Florian's outdated e-mail address with a valid BMW address.

• need to at least be able to ignore certain objects of configurable types

Feedback from users with read-green weakness is that, they cannot distinguish the background coloring of the lobster HTML report. For some red and gray look very similar, for others it is red and green.

1. use different colors
2. use icons additionally to indicate "error", "justified exemption" and "ok".

Requirement A that inside one level is decomposed into B and C, would be OK if B and C are themselves OK.

Policy example:

requirements "Requirements" {
   source: "potato.lobster";
}

implementation "Code" {
   source: "code.lobster";
   trace to: "Requirements" with internal_links;
}

activity "Test" {
   source: "test.lobster";
   trace to: "Requirements";
}

OR perhaps allow self-references:

requirements "Requirements" {
   source: "potato.lobster";
   requires: "Code" or self_reference;
   requires: "Test";
}

implementation "Code" {
   source: "code.lobster";
   trace to: "Requirements"
}

activity "Test" {
   source: "test.lobster";
   trace to: "Requirements";
}

Would allow for example:

      R1
     / \
    R2  R3
    |   |
    C2  C3

As long as all requirements are individually tested.

Side-note: We now need to worry about cycles, i.e. R1 -> R2, R2 -> R1 and should make sure that these do not count.

This check only needs to be done for levels that allow self_references.

e.g.

activity "test" {
  trace to: "system requirement" or "software requirement";
}

e.g. --min-required-coverage=95

Please create a "vanilla example" that demonstrates how to do the following:

• extract one requirement from a TRLC file with lobster-trlc
• extract one function from a Python file with lobster-python
• extract one test from a Python file with lobster-python --activity
• extract one function from a C++ file with lobster-cpp
• extract one requirement from codebeamer with lobster-codebeamer

and put it all together in a tracing policy, and generate an HTML lobster report.

Please think about the best way to publish the vanilla example. Maybe it is a good idea to provide a zip file, so that it easy extremely easy to download it.

The goal is to train interested users quickly how to use lobster.

If lobster-python runs over a Python project where unittest is used instead of pytest, then each test is also interpreted as a regular function.
This leads to the result that the final lobster report shows each unit test twice (as a function and as a test).

We need to check if this happens only for unittest, or also for pytest.

For example

{
   "name": "foo",
   "requirements": [1, 2, 3]
}

Especially the lobster trace stuff should support plugins, so that you can add/install modules with a magic name and things just work.

perhaps in lobster-ci-report an additional flag --show-justifications

One entry point with commands, e.g.

• lobster trace cpp <stuff...>
• lobster trace matlab <stuf...>
• lobster report [ --html | --ci ]
  etc.

Parse C++ fragment directly