in reply to Re: Testing with non-trivial input
in thread Testing with non-trivial input

Hello dws,

Nearly a year on and I am again faced with this problem. Back then I missed your reply. What you suggest does seem like a good solution. However, wouldn't I have to worry about whitespace issues when defining the expected XML output?

Thanks,

loris

BTW, "the input for this" meant the information about which fragment of XML to extract was contained in a line of the CSV file.

"It took Loris ten minutes to eat a satsuma . . . twenty minutes to get from one end of his branch to the other . . . and an hour to scratch his bottom. But Slow Loris didn't care. He had a secret . . ."

Replies are listed 'Best First'.
Re^3: Testing with non-trivial input
by dws (Chancellor) on Oct 12, 2005 at 18:11 UTC

    wouldn't I have to worry about whitespace issues when defining the expected XML output?

    Yes, but you only have to worry about it once. In fact, it's good to get a test that fails based on whitespace, since examining the output will give you confidence that the test (once the whitespace is corrected) is testing what you expect.