Currently lobster-codebeamer creates an error message if the codebeamer item does not have a summary, see
https://github.com/bmw-software-engineering/lobster/blob/64104c547f4adcb299b04bc118287d229f075e69/lobster/tools/codebeamer/codebeamer.py#L200
However, it is a legit use case to have codebeamer items without a summary. For example, some projects might decide to use only the description in codebeamer, and keep the summary empty. A possible reason for such a decision could be that, the requirements have been migrated from another database into codebeamer, and there was no summary field available in the previous database.
lobster-codebeamer currently creates a message in the resulting JSON file, and lobster-report then ignores the item in the computation of the coverage, and lobster-html-report prints an error message into the HTML report.
Hence I recommend to remove the restriction from lobster-codebeamer.
Currently
lobster-codebeamercreates an error message if the codebeamer item does not have a summary, see https://github.com/bmw-software-engineering/lobster/blob/64104c547f4adcb299b04bc118287d229f075e69/lobster/tools/codebeamer/codebeamer.py#L200 However, it is a legit use case to have codebeamer items without a summary. For example, some projects might decide to use only the description in codebeamer, and keep the summary empty. A possible reason for such a decision could be that, the requirements have been migrated from another database into codebeamer, and there was no summary field available in the previous database.lobster-codebeamercurrently creates a message in the resulting JSON file, andlobster-reportthen ignores the item in the computation of the coverage, andlobster-html-reportprints an error message into the HTML report.Hence I recommend to remove the restriction from
lobster-codebeamer.