Support Python 3.13 #255
Closed
Support Python 3.13 #255
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update for traceability report use cases related to 'C++ tests' and 'Codebeamer requirements'. - lobster/tools/requirements.rsl: File updated with addition of 'type UseCase' for Use case writing. - lobster/tools/UseCase.trlc : New file added to define use cases. The use cases for traceability report between 'C++ tests' and 'Codebeamer requirements' are added in the file.
Remove the assertion from the `TestRunner` class which made sure that the root folder name is equal to `lobster`. This assertion fails if the local repository folder has got a different name. Issue: #229
Setup unit test based system test infrastructure (STF) for lobster-report. Migrated a system test for status OK to STF.
Update the workflow in `ci.yml` such that linting is done first, and tests are executed only if linting succeeded. (Previously tests did not depend on `lint-system-tests`, but only on `lint`.)
Add a chapter to the `tests-system/README.md` file that explains how to setup VSCode such that it is possible to run/debug system tests.
Co-authored-by: Philipp Wullstein-Kammler <[email protected]>
The integration tests use TRLC files. The package names in these TRLC files are now aligned with the folder name that contains the integration test files.
On the one hand it is necessary to run the system and unit tests in order to create the branch coverage report. The system tests require that graphviz is NOT installed, otherwise they fail. On the other hand, the LOBSTER reports shall show the visualization of the tracing policy, so graphviz must be available for their generation. The `docs.yml` workflow creates all reports and publishes them to GitHub pages. Hence the order of steps matters: 1. generate the branch coverage reports 2. install graphviz 3. generate the LOBSTER traceability reports
The LOBSTER Json command line arguments are now converted to Yaml config file arguments. This PR also contains modification for some common functions in LOBSTER_Tool class.
Implemented LOBSTER_Tool class for LOBSTER TRLC and modified CHANGELOG, Readme, small bug fix in mandatory parameters validation. With this implementation the lobster TRLC will start using YAML config for command line tools except for "--out" & "--config" parameters. All the related system testcases, unit testcases and integrations test cases are modified.
Requirements for lobster-trlc config parameters - - inputs - inputs_from_file
System test infrastructure is implemented for lobster-trlc. 6 system test cases added. Co-authored-by: Kedar Navare <[email protected]>
System testcase for lobster-trlc added. The test case covers a happy scenario when both the `inputs` and `inputs_from_file` options are given.
If no inputs are given then, check that current working directory is consumed
This PR contains the following: - Added a scenario for "File is given once in “inputs_from_file” and same file is given in “inputs”, check that “duplicate_definition” error is produced" - Added lobster traces for lobster-trlc system test cases.
Migrated following lobster-report system tests to STF - Missing - Justified - Ok - made changes in OK status system test
When running `lobster-python --activity` the tool assumes that Python methods with the following name pattern are tests: - name starting with `_test` or `test` - or name ending with `test`
Include Python 3.13 in the test matrix.
phiwuu
force-pushed
the
feature/support-python313
branch
from
fcb6df9 to
03bae04
Compare
kedarnn
force-pushed
the
feature/support-python313
branch
from
03bae04 to
af37b0c
Compare
Member
Author
|
Follow-up PR: #378 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Include Python 3.13 in the test matrix.