-
Notifications
You must be signed in to change notification settings - Fork 62
test: add usecase test interceptor #2486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ap891843
merged 2 commits into
eclipse-che4z:development
from
ap891843:use-case-test-interceptor
Sep 20, 2024
Merged
test: add usecase test interceptor #2486
ap891843
merged 2 commits into
eclipse-che4z:development
from
ap891843:use-case-test-interceptor
Sep 20, 2024
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
Signed-off-by: ap891843 <[email protected]>
49f2177
to
66b7a46
Compare
server/engine/src/test/java/org/eclipse/lsp/cobol/usecases/suite/UniqueIdTestWatcher.java
Outdated
Show resolved
Hide resolved
server/test/src/main/java/org/eclipse/lsp/cobol/test/engine/ExtensionContextCleaner.java
Outdated
Show resolved
Hide resolved
server/test/src/main/java/org/eclipse/lsp/cobol/test/engine/UseCaseEngine.java
Show resolved
Hide resolved
server/test/src/main/java/org/eclipse/lsp/cobol/test/engine/UseCaseEngine.java
Show resolved
Hide resolved
Signed-off-by: ap891843 <[email protected]>
slavek-kucera
approved these changes
Sep 19, 2024
ap891843
added a commit
that referenced
this pull request
Mar 14, 2025
* test: add usecase test interceptor Signed-off-by: ap891843 <[email protected]> * fix: update as per PR comments Signed-off-by: ap891843 <[email protected]> --------- Signed-off-by: ap891843 <[email protected]>
ap891843
added a commit
to ap891843/che-che4z-lsp-for-cobol
that referenced
this pull request
Mar 26, 2025
A regression was introduced in 5.11.0-M2 as part of PR junit-team/junit5@bc87b07 This resulted in failures to create usecase test files when run with "usecase.test.repo.dir" flag (eclipse-che4z#2486). Signed-off-by: amanprashant <[email protected]>
ap891843
added a commit
that referenced
this pull request
Mar 26, 2025
A regression was introduced in 5.11.0-M2 as part of PR junit-team/junit5@bc87b07 This resulted in failures to create usecase test files when run with "usecase.test.repo.dir" flag (#2486). Signed-off-by: amanprashant <[email protected]>
mm-broadcom
pushed a commit
to mm-broadcom/che-che4z-lsp-for-cobol
that referenced
this pull request
Apr 9, 2025
A regression was introduced in 5.11.0-M2 as part of PR junit-team/junit5@bc87b07 This resulted in failures to create usecase test files when run with "usecase.test.repo.dir" flag (eclipse-che4z#2486). Signed-off-by: amanprashant <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Each test could be run with
-Dusecase.test.repo.dir=<path_for_testcase_source>
, this would generate a subfolder folder under provided path_for_testcase_source with following structure and place cobol source(source.cbl
), copybooks(files with.cpy extensnsion
and a marker files indicating if Cobol LS engine expects 0 diagnostics)class name --> test method name --> parameter number (if present)
Checklist: