I have noticed several unit test failures lately in Shindig (Java). Is
anyone working on fixing these?
Failed tests:
testTagContentWithPrint(
org.apache.shindig.gadgets.servlet.ETaggingHttpResponseTest):
Unexpected method call setHeader("ETag",
"ffd6df83a34ede3c4d5a61284596ea37"):
setHeader("ETag", "dae018f624d09423e7c4d7209fbea597"): expected: 1,
actual: 0
setContentLength(14): expected: 1, actual: 0
testNotModifiedWithPrint(
org.apache.shindig.gadgets.servlet.ETaggingHttpResponseTest):
Unexpected method call setHeader("ETag",
"ffd6df83a34ede3c4d5a61284596ea37"):
setHeader("ETag", "dae018f624d09423e7c4d7209fbea597"): expected: 1,
actual: 0
setStatus(304): expected: 1, actual: 0
setContentLength(0): expected: 1, actual: 0
testNonMatchingETagWithPrint(
org.apache.shindig.gadgets.servlet.ETaggingHttpResponseTest):
Unexpected method call setHeader("ETag",
"ffd6df83a34ede3c4d5a61284596ea37"):
setHeader("ETag", "dae018f624d09423e7c4d7209fbea597"): expected: 1,
actual: 0
setContentLength(14): expected: 1, actual: 0
testStreamingMode(
org.apache.shindig.gadgets.servlet.ETaggingHttpResponseTest): array
lengths differed, expected.length=14 actual.length=19
testCanCalculateHashSeveralTimes(
org.apache.shindig.gadgets.servlet.ETaggingHttpResponseTest):
expected:<[dae018f624d09423e7c4d7209fbea59]7> but
was:<[ffd6df83a34ede3c4d5a61284596ea3]7>
testHashVariesAsDataIsAdded(
org.apache.shindig.gadgets.servlet.ETaggingHttpResponseTest):
expected:<[dae018f624d09423e7c4d7209fbea59]7> but
was:<[ffd6df83a34ede3c4d5a61284596ea3]7>
Tests run: 1529, Failures: 6, Errors: 0, Skipped: 5
-Ryan
Email: [email protected]
Phone: 978-899-3041
developerWorks Profile
