Hi Bob, bobsmith1@marketweighton.com wrote:
What the user sees is different from the content of what the user sees.
if you already have xml for the content, and generate html out of it, then you basically have my idea, but...:
I read the book eXtreme Programming(by kent beck), and I'm also a fan of testdriven development, so using xml for the content means we can write automated tests for the entire OTRS application, and separate the output of the application (XML) with user interface packages(in (X)HTML)....that's my idea...I haven't ever looked at the code of otrs so I don't know what you are doing in there. It also would mean that we can have tests at the customer site, and simply run them to validate that the application behaves like it should behave.
so basically: application output---->xml---->html----->visual content | | +-------->tests--->>validation for correct operation--->money
each package in OTRS would come with a test suite, which checks the output of the application ( XML + dtd) and validates that the output is conformant to the package test criterias, that way we can be sure that OTRS behaves like we want it to behave, the only thing left to test/validate would be exactly how the application looks (what the user sees)...( look and feel )
what do you think? do you already do it this way?
I like this way of testing. This should be a way for the frontend testing which we should go. But this means also to change the OTRS core in a really hard way. -=> We can think about it in new mayor releases (e. g. OTRS3 or OTRS4). PS: We like people with new ideas. If you want to get involved, feel free to contact us. :)
best R /G
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!