> >>2.) There are tests that seem to be specific to Tamino. What > >>to do with > >>them? > > > > > > Of course, as discussed in previous mails, these should be > removed. Can you > > tell which exactly are Tamino-specific? (our testsuite > expert is currently > > out of office :)) If you haven't a list already, I can find out. > > There are some tests involving XML specific stuff indicating they > *might* check for some Tamino internals, but I really do not > think they > should be removed. These tests cause problems as they try to work on > /slide/administration (where access is forbidden) which I guessed is > Tamino specific: > > testsuite\junit\xmltestcases\functional\delete\code\Delete403File.xml > testsuite\junit\xmltestcases\functional\delete\code\Delete403Col.xml
OK, testcases operating on /slide/administration can be deleted. > >>3.) Tests with LOCK method expect as owner "/slide/users" (as > >>replaced > >>by "some owner"), but when being unauthenticated you are > >>"/slide/unauthenticated". Shouldn't URI of unauthenticated be > >>in users > >>as well? Like "/slide/users/unauthenticated"? Or should "some > >>owner" be > >>less restrictive? > > > > > > I didn't test very much with authentication switched-off > yet. My plan was to > > let the unauthenticated user have just "unauthenticated" as > URI. Possibly > > it's a bad idea ... in which case the URI should be > > /slide/users/unauthenticated and not > /slide/unauthenticated. I can take care > > as soon as I get a chance ... :) > > I think /slide/users/unauthenticated or /slide/unauthenticated is a > matter of taste. What works for me here is to set "some owner" to > /slide/unauthenticated in TProcessor.CMD when in "no authentication" > mode. Shall I check this in? OK, go ahead. Regards, Peter
