Its free to try for 1 month
BWUnit v14 has been released. We’ve been working hard on a bringing you coverage reports to show you what BW processes and activities are being tested, and which ones aren’t. The XML reports integrate easily with Jenkins, allowing you to easily see where you need to increase your testing and how your coverage has changed over time. We hope you’ll love this new feature as much as we do.
The `run-tests` macro can now produce Emma compatible XML test coverage reports, which lets you quickly determine what processes and activities aren’t being tested.
When an AssertEqual fails, it will now provide you with an XML diff of the expected and actual XML nodes, allowing you to quickly determine what and where the difference is.
The `run-tests` macro now accepts a time-out attribute, which will be passed to the BW engine, so that you can have the engine automatically shutdown after the specified amount of time.
The ‘Test sendCustomerFax’ test was failing when running the BWUnit service from within designer.
If ASCII encoded characters are passed into the assert message and those characters conflict with UTF8 control characters, then the ant scripts will not generate results.
when a property is mapped to BWUnit/HTTP-service-port, the run-test macro is not detecting it correctly and fails to detect when the engine is started.
The failonerror attribute int he run-tests macro is supposed to cause the build to fail if it is true and there is a test failure. At the moment if only fails the build if the communication between the ant scripts and the BW engine.
The template project cannot retrieve BWUnit, due to an error in config/ivysettings.xml
BW 5.10 has a defect that prevents BWUnit’s HTTP receiver from functioning correctly. Switching from Tomcat to HTTPComponent for the transport resolves this issue.
In order to control the code that gets executed after a failed test run, as a developer, I should be able to have `run-tests` set a property when the tests fail