citrus
citrus copied to clipboard
citrusframework
Framework for automated integration tests with focus on messaging integration
- Improve constructors to only use builder instead of redundant condition and builder Fixes #861
conventional commits are the de facto standard for keeping git history clean, automatic versioning and release notes and/or changelog generation. that is one possibility, tho Maven integration is almost non-existent....
during the build phase of [email protected] there are a lot of warnings. the log lines will be prefixed by "WARNING", that allows a good filtering. these come from unsafe casts...
as the title states.. migrate the internal tests from testng to junit jupiter.
**Citrus Version** 3.2.1 **Expected behavior** The constructor should set the condition in the underlying builder. **Actual behavior** The constructor does not set the condition in the underlying builder, it has...
**Citrus Version** 3.1 (applies to current version of Citrus-Simulator as well) **Expected behavior** Usage of loggers should be unique over all classes and modules **Actual behavior** Currently loggers are instantiated...
**Citrus Version** **Question** - Can you please provide a sample for Kafka integration over SSL? **What I've tried so far** **Additional information**
Citrus Version: at least 3.2.0 & 3.2.1 --- Expected behavior: When a fat jar is built, started and then triggered, the http server should be started. --- Actual behavior: Tests...
# Related to #83 ## Scenario: Trying to use TestNG DataProvider together with TestRunner resource injection. DataProvider attribute parallel = true ## Testcase: public class DataProviderTest extends TestNGCitrusTest { private...
Metadata
Owner
Metadata
Framework for automated integration tests with focus on messaging integration