So I need two different users. One creates, the second copies. The copy should have the second user as owner.
I always test with authnetication enabled, so I've never seen any problems with introduding this test case. May be we should move it to
multiuser test cases?
Stefan
Oliver Zeigermann wrote:
That's right! Authentication is not enabled! Why is it required to be enabled?
Oliver
Stefan L�tzkendorf wrote:
I use the default Domain.xml with an additional store for files_second..
Authnetication must be enabled. It seems that you are running the webapp without authentication.
Stefan
Oliver Zeigermann wrote:
This is the report of on of the failed test cases:
Tue Aug 03 14:18:49 CEST 2004 Starting test case: e:\workspace\Slide HEAD\testsuite\bin\..\testsuite\junit\xmltestcases\functional\copy\copyChangedProperties.xml
<testCase>
<fileName>e:\workspace\Slide HEAD\testsuite\bin\..\testsuite\junit\xmltestcases\functional\copy\copyChangedProperties.xml</fileName>
<exceuteStep> <method>PUT</method> <url>/slide/files/help-doc.html</url> <result>Success</result> <time>9297</time> </exceuteStep> <exceuteStep> <method>COPY</method> <url>/slide/files/help-doc.html</url> <result>Success</result> <time>8344</time> </exceuteStep> <exceuteStep> <method>PROPFIND</method> <url>/slide/files/copy.html</url> <XMLNameError> <path>/multistatus/response/propstat/prop/owner</path> <expectedName>href</expectedName> <receivedName>unauthenticated</receivedName> </XMLNameError> <XMLValueError> <path>/multistatus/response/propstat/prop/owner/href</path> <expectedValue>slide/users/unauthenticated2</expectedValue> <receivedValue /> </XMLValueError> <result>ERROR</result> <time>953</time> </exceuteStep> <exceuteStep> <method>DELETE</method> <url>/slide/files/help-doc.html</url> <result>Success</result> <time>1110</time> </exceuteStep> <exceuteStep> <method>DELETE</method> <url>/slide/files/copy.html</url> <result>Success</result> <time>1297</time> </exceuteStep> <result>ERROR</result> <time>21906</time> <testElementCount>5</testElementCount> <testElementErrors>1</testElementErrors> </testCase>
Stefan L�tzkendorf wrote:
After having some trouble with weird errors ... with the latest CVS head I couldn't reproduce any of that errors (without any changes from my sides)
Can I get a result.xml to have a look at it if the problem still exists.
Regards Stefan
Oliver Zeigermann wrote:
Did the same thing for the SQLServer store. It revealed the same 3 failed test cases. I remember that Stefan (L�tzkendorf) has introduced them, right?
Stefan, could you have a look at it?
Oliver
Oliver Zeigermann wrote:
Folks!
I have just run the test suite on the the present Slide version with the default file store. Would someone volunteer to do the same for the RDBMS stores and report back the results?
Anyway, here are the failed tests:
- testsuite\junit\xmltestcases\functional\copy\copyChangedProperties.xml
- testsuite\junit\xmltestcases\functional\notification\pollUpdateCollDepthInfinit.xml and
testsuite\junit\xmltestcases\functional\notification\pollUpdateCollDepthOne.xml
- all multistore tests
Nothing critical, but we should find out the reasons for the failures. Anyone any idea?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
