2.9.3. Limitations of the converter
Prev | 2.9. Converting a project into API (experimental) | Next

### 2.9.3. Limitations of the converter

Current known limitations of the converter

- If two Test Cases exist with the same name in the same category, only one of them will be converted

- If a Test Job and a Test Suite exist with the same name in the same category, only one of them will be converted

- Names of Test Cases,Test Suites and Test Jobs should match the Java conventions for class names. However we are doing some minor adjustments to names like removing spaces. (see Java language specification)

- Test Cases,Test Suites and Test Jobs should not begin with numbers

- There are actions which are not convertible (Store value, Read/Start Timer, Manual Test Step, restart and synchronize, restart, execute external command)

- Event Handler will not be active after conversion. They need to be changed and other code might be necessary to work in the client-api

- AUT configurations are not converted

- The first AUT is used to determine the toolkit of the project