Thanks Martin, but that does not make any sense from what I am seeing. So, to better highlight, I have created two tests that are identical in every way except:Test 1:tester.assertResultPage(expectedDocument1())Test 2:tester.assertResultPage(expectedDocument2())Method expectedDocument1() looks like:Method expectedDocument2() looks like:The only difference between the two is the addition of the trailing line return added to the second string. This results in two different, and confusing stack traces.The first stacktrace:This is what you saw in the original post and it appears that all that was required was to add the aforementioned newline. However, contrast that with the results from the second test:What is most interesting is not that the expected strings look different in the two sets, but that the results do. Why would they be inconsistent? It makes absolutely no sense. And with the expected strings looking different in the two tests, something gravely wrong is going on. I tried to use highlighting, but it does not work in the "raw" code for obvious reasons (in retrospect). It might be helpful to look at in a merge/comparison tool.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/assertResultPage-fails-even-when-same-tp4654830p4654863.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
