|
From: Artem Y. <ne...@gm...> - 2008-07-09 00:59:17
|
Waylan Limberg wrote: > I then found lxml's htmldiff tool [1], which provided an easy > (better??) way to compare html docs, but it still hung up on some (not > all) whitespace. Additionally, it didn't exactly provide an easily > readable output to display in the test output. If your interested, I > can forward the code I have - that is, if I can find it. > Yep, it would be interesting. > What I'd consider doing is actually taking the most recent markdown > with NanoDom and altering NanoDom's whitespace to match ET and run a > little script that loops through all the tests and outputs new > expected html files. It shouldn't be all that hard. > Yes, for now it seems reasonable solution. Also, ET don't have any output indentation, I wrote function that do some indentation for ET. Another one solution is to tune this function to match previous markdown output. I also tried to load data from tests html files to ET, and then serialize it, but there are some issues and I didn't succeeded in it. |