Duette supports importing results from QTP, RFT, Selenium (HTML format) and unit testing frameworks.
For unit test frameworks ET supports a number of different formats (Gallio, JSUnit,JUnit, Microsoft MSTest, Parasoft C++test and PHPUnit). Prior to being imported, ET transforms each of these formats into the JUnit XML results format (a popular Java unit test framework).
If you have bespoke unit testing data that you want to import into Enterprise Tester, you can create bespoke tooling to transform your results into JUnit XML format. Once your results are transformed, they can then be imported into Duette.
This page documents the JUnit XML format itself.
Here is an example of a JUnit output file, showing a skip and failed result, as well as a single passed result.
Below is the documented structure of a typical JUnit XML report. Notice that a report can contain 1 or more test suite. Each test suite has a set of properties (recording environment information). Each test suite also contains 1 or more test case and each test case will either contain a skipped, failure or error node if the test did not pass. If the test case has passed, then it will not contain any nodes. For more details of which attributes are valid for each node please consult the following section "Schema".
The JUnit XML Report output comes from a build tool called Nant, as opposed to the JUnit project itself - thus it can be a little tricky to nail down an official spec for the format, even though it's widely adopted and used. There have been a number of attempts to codify the schema, first off there is an XSD for JUnit:
Relax NG Compact Syntax
There is also a Relax NG Compact Syntax Schema:
The JUnit XML report format originates the JUnit ANT task - this is the definitive source for the JUnit Report XML format - and source code can be found on the apache SVN repository here:
This can be useful if attempting to do anything "tricky" with JUnit output where you need to confirm it's compliant.
Stack Overflow Discussions
Here are some additional topics on stack overflow that discuss the JUnit XML format which can be useful for learning about the schema for the JUnit XML results format, as well to get hints about what minimum subset is normally suitable for most tools such as Jenkins (the same rules apply to ET generally as well).