Skip to Content

Detroubulator version 1.1: Bits and pieces

This is my second blog post about the upcoming version 1.1 of Detroubulator, our open source unit test tool for SAP XI mapping programs. In the Detroubulator version 1.1: New features, part 1 I discussed expected values in assertions. This post contains various bits and pieces of information about version 1.1. In the next post I’ll blog about another new feature.

Java 6 based

Version 1.1 of Detroubulator requires a Java 6 runtime to run, whereas version 1.0 only requires Java 5. This means that if you have yet to install Java 6, you will need to do so in order to run the new version. We realize that this is an inconvenience, but hope that you’ll find the new features compelling enough to upgrade.

100% command line

Detroubulator version 1.0 was intended to be a 100% command line application. However, at the time it wasn’t possible to prompt for a password on the command line in Java in a way that was both portable and secure. For this reason, we ended up implementing the XI server logon as a GUI window. In version 1.1 the logon window is gone, making Detroubulator a true blue command line app. The password prompting is performed using, which is a new class in the Java 6 class library. The Console class has a readPassword method that reads characters from the command line without echoing them back.

Backwards compatibility

Even though the Detroubulator application itself now requires a Java 6 runtime, the test file format remains 100% backwards compatible with the original version 1.0 format. All new elements and attributes in the test file schema are optional. This ensures that your old test files will remain valid and will work as expected in version 1.1.

Release schedule

We’re currently aiming for a late May/early June release of Detroubulator version 1.1. If you’re feeling brave and you simply cannot wait, you can always check out the latest source from Google Code and build the application yourself. Be advised, though, that we’re still making changes to the code, so it might not always work as expected (or even compile, for that matter).


We’ve received reports of tests that start failing out of nowhere. Our preliminary investigations indicate that this guy might have something to do with it:

Detroubulator lolcat

Keep your eyes peeled for him 🙂

Be the first to leave a comment
You must be Logged on to comment or reply to a post.