B
Ben Burdick
I am somewhat new to ruby and would appreciate any help on this
matter. I have a custom assertion for running tests
"assert_valid_xml_response" - which will parse the output and check
for any bad xml..
My problem is, that with many changes constantly taking place, and
many of these assertions taking place, it is sometimes hard to
pinpoint exactly where the bad XML is hiding.
Has anyone stumbled across a solution to easily zero in on the
location of bad XML?
matter. I have a custom assertion for running tests
"assert_valid_xml_response" - which will parse the output and check
for any bad xml..
My problem is, that with many changes constantly taking place, and
many of these assertions taking place, it is sometimes hard to
pinpoint exactly where the bad XML is hiding.
Has anyone stumbled across a solution to easily zero in on the
location of bad XML?