tschlat
tschlat
**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...
**User story** As a test designer who uses the citrus spring integration, I would like support in managing my template contexts. Template contexts are contexts which contain elements - reusable...
**User story** As a tester I would like to have detailed information on my test execution. Very important information are the messages send and received during execution. I want to...
**Citrus Version** 3.1.0 **Expected behavior** If I run more than one JUnitTest (Class) via CitrusSpringExtension, I would expect that the results of all TestCases over all TestClasses are collected and...
**Citrus Version** 3.1.0 **Expected behavior** Citrus logs the test execution statistics via TestReporters.generateReports at the end of a test suite execution. **Actual behavior** If Logback is for example used as...
When providing exploded query parameters in a message for the simulator, an exception is thrown caused by the algorithm that collects the queryParams for the message. Regards, Thorsten `java.lang.IllegalStateException: Duplicate...
**Citrus Version** 4.0 **Expected behavior** Citrus should be able to run from a Spring Boot application. **Actual behavior** Citrus does not resolve all required components like validators etc. These are...
**User story** As a *developer*, I want to generate a test API so that I can test OpenAPI-specified services efficiently. **Additional context** This feature request aims to provide a tool...
I have added code for the test API generator plus documentation. The generator has been implemented having XML tests in mind. Therefore, usage within Java DSL is a little cumbersome...
Added these changes for implementation of HttpScenarioGenerator using the OpenApi Connector.