-
Notifications
You must be signed in to change notification settings - Fork 5
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
Adapt Java integration tests for new ScriptOptions parser #988
Labels
refactoring
Code improvement without behavior change
Comments
This was referenced Oct 21, 2024
Merged
tomuben
added a commit
to exasol/script-languages
that referenced
this issue
Oct 22, 2024
tomuben
added
refactoring
Code improvement without behavior change
and removed
feature
Product feature
labels
Oct 29, 2024
tomuben
added a commit
to exasol/script-languages
that referenced
this issue
Oct 30, 2024
tomuben
added a commit
that referenced
this issue
Oct 30, 2024
10 tasks
10 tasks
tomuben
added a commit
that referenced
this issue
Oct 30, 2024
tomuben
added a commit
that referenced
this issue
Nov 5, 2024
Changelist: - #969: Use new CTPG parser in java vm (#970) - #980: Moved flavor template-Exasol-all-java-17 to script-languages repo (#984) - #971: Removed dead code in Java VM (#985) - #982 & #983: Refactorings in ScriptOptions parser (#987) - #988: Adapted Java integration tests for new ScriptOptions parser (#995) - #997: Added documentation for Rollback of Script-Languages-Container (#999)
tomuben
added a commit
that referenced
this issue
Nov 14, 2024
Changelist: - #944: Removed exaudfclient_bin_py3 (#975) - #967: Added ctpg script options parser (#968) - #972 and #973: Refactorings for Script Options parser (#976) - #977: Fixed Trivy update cache workflow (#978) - #969: Use new CTPG parser in java vm (#970) - #980: Moved flavor template-Exasol-all-java-17 to script-languages repo (#984) - #971: Removed dead code in Java VM (#985) - Refactorings in ScriptOptions parser (#987) - #988: Adapted Java integration tests for new ScriptOptions parser (#995) - #997: Added documentation for Rollback of Script-Languages-Container (#999) - #878: Fixed jvmoption and parameters containing a space (#1001) - #1002: Use ECR fallback repository for Trivy caching (#1004) - #1006: Updated Dependencies on top of 8.4.0 (#1007) - #958: Fix conda version conflict (#1010) - #1009: Removed NVIDIA GPU Driver Libraries from template-CUDA SLC (#1012) - Bumped version to 9.0.0 (#1013) - #1014: Fixed Push Docker Test Container workflow (#1015)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
We have implemented the new Script Options parser in the UDF client. In #986 we added new option in the UDF clients which activates the new parser.
With the new option implemented, we can adjust the integration tests for Java, to run for both the legacy parser and the new parser. It makes sense to run the tests twice only for tests where the script options are being used.
Acceptance Criteria
Java integration tests which use Script Options should be executed with both parser versions.
The text was updated successfully, but these errors were encountered: