-
Notifications
You must be signed in to change notification settings - Fork 136
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
Add JBang support #1049
Comments
christophd
added a commit
that referenced
this issue
Nov 6, 2023
- Introduce TestSource model that holds polyglot test sources (.xml, .yaml, .groovy, .feature) - Enhance TestNG TestEngine implementation to support running polyglot Citrus tests (xml, yaml, groovy) - Enhance Cucumber TestEngine to properly handle feature files passed to the run command - Introduce citrus-jbang module in tools - Add JBang catalog pointing to Citrus JBang CLI script - Add CitrusJBangMain script with following commands - Init command to create test template (.yaml, .xml, .groovy, .feature) - ListTests command list all running tests - Run command able to run tests via TestEngine API - Fix java util logging to send all log events to SLF4J
christophd
added a commit
that referenced
this issue
Nov 6, 2023
- Introduce TestSource model that holds polyglot test sources (.xml, .yaml, .groovy, .feature) - Enhance TestNG TestEngine implementation to support running polyglot Citrus tests (xml, yaml, groovy) - Enhance Cucumber TestEngine to properly handle feature files passed to the run command - Introduce citrus-jbang module in tools - Add JBang catalog pointing to Citrus JBang CLI script - Add CitrusJBangMain script with following commands - Init command to create test template (.yaml, .xml, .groovy, .feature) - ListTests command list all running tests - Run command able to run tests via TestEngine API - Fix java util logging to send all log events to SLF4J
christophd
added a commit
that referenced
this issue
Nov 9, 2023
- Introduce TestSource model that holds polyglot test sources (.xml, .yaml, .groovy, .feature) - Enhance TestNG TestEngine implementation to support running polyglot Citrus tests (xml, yaml, groovy) - Enhance Cucumber TestEngine to properly handle feature files passed to the run command - Introduce citrus-jbang module in tools - Add JBang catalog pointing to Citrus JBang CLI script - Add CitrusJBangMain script with following commands - Init command to create test template (.yaml, .xml, .groovy, .feature) - ListTests command list all running tests - Run command able to run tests via TestEngine API - Fix java util logging to send all log events to SLF4J
@christophd has this module (tools/jbang) been published yet? I mean, can I try and use it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JBang is a great tool for Java scripting. JBang allows users to run Java scripts in an easy and comfortable way.
Citrus JBang would allow the user to create/run tests very fast without much of a project setup. The user may use this for rapid prototyping and as a starting point for a new Citrus project with some export functionality.
Possible commands could look like this
$ jbang citrus init hello.yaml $ jbang citrus run hello.yaml $ jbang citrus ls PID NAME STATUS AGE 1234. hello RUNNING 15s $ jbang citrus logs hello ... $ jbang citrus export --maven
Popular JBang implementations are the one provided by Apache Camel: https://camel.apache.org/manual/camel-jbang.html
The text was updated successfully, but these errors were encountered: