LOBSTER Report - no schema#524
Conversation
For future use we want to support a yaml file as config file fore the lobster_report tool. During implementation and testing phase the known .conf file still can be used.
For future use we want to support a yaml file as config file fore the lobster_report tool. During implementation and testing phase the known .conf file still can be used.
For future use we want to support a yaml file as config file fore the lobster_report tool. During implementation and testing phase the known .conf file still can be used.
…oftware-engineering/lobster into vtt/lobster_report_no_kind
For future use we want to support a more flexible configuration. Therefor we remove the schema (requrement, implementation, code) from the lobster files. Version without schema is 5. All items are now from base Item class. Remove schema from .lobster files with version 5. Only write Item's to get remove Requirement, Implementation and Acticity in the future. For transition period the old versions are still supported.
Remove schema from .lobster files with version 5. Only write Item's to get remove Requirement, Implementation and Acticity in the future. For transition period the old versions are still supported.
fix pylint
Remove schema from .lobster files with version 5. Only write Item's to get remove Requirement, Implementation and Acticity in the future. For transition period the old versions are still supported.
fix pylint
…re-engineering/lobster into vtt/lobster_report_v2
fix pylint fix bazel integration
c624f5f to
2a74d83
Compare
add missing files
exclude yamale files for integration test diff
fix pylint fix bazel integration exclude yamale files for integration test diff
integration tests: adjust expected output
…re-engineering/lobster into vtt/lobster_report_v2
integration tests: adjust expected output
# Conflicts: # tests_system/lobster_codebeamer/lobster_codebeamer_test_runner.py
mugdhadhole1
left a comment
There was a problem hiding this comment.
Since both old and new code currently run and the old one will be removed later, it will be very helpful if a comment exists marking where the old code exists.
|
I'm attaching an example where I attempted to generate the HTML report. |
adjust PR findings
adjust PR findings
adjust to new port handling of LobsterCodebeamerAsserter
adjust PR findings
adjust PR findings
…re-engineering/lobster into vtt/lobster_report_v2
There was a problem hiding this comment.
Why is this folder added at root level?
| The tool supports three configuration attributes: | ||
| `output_file`, `codebeamer_url` and `files`. |
There was a problem hiding this comment.
For the deprecated functionality the user still need to give kind. So I think over here we need to have documentations for both the usages.
| @@ -0,0 +1,15 @@ | |||
| Requirements: !LevelDefinition | |||
There was a problem hiding this comment.
I could not find any references to this file in tests, docs, or build targets.
Resolve merge conflicts.
Fixed Pylint issues that were introduced by the previous merge commit. Also improved one docstring.
| def test_lobster_read_missing_versio_key(self, mock_file_open, mock_isfile): | ||
| with self.assertRaises(LOBSTER_Error): | ||
| lobster_read(self.mh, self.filename, self.level, self.items, self.source_info) | ||
| self.mh.error.assert_called_with(ANY, "required top-level key version not present") |
There was a problem hiding this comment.
- Method
errorhas noassert_called_withmember (no-member) - Undefined variable
ANY(undefined-variable)
(detected by pylint)
Remove schema from .lobster files with version 5.
Only write Item's to get remove Requirement, Implementation and Acticity in the future.
For transition period the old versions are still supported.
Introduce new yaml config file for LOBSTER report.