Show HN: Houdini – A new way to test web apps

Re:Show HN: Houdini – A new way to test web apps by aantix on Wednesday January 15, 2014 @04:45PM (#7066397)

In the dynamic content example; with the previous showing one item and the second screen shot showing two items, what is it about the DOM structure that makes this a passing test? How do you know that the functionality wasn't suppose to update an item?

Wouldn't you at least need three tests; an initial test to show that an item is inserted into the DOM, a second test to demonstrate that the system is inserting, not updating an item, and then finally your third test that demonstrates the functionality continues to insert into the DOM?

[ Parent | on HN ]

Re:Show HN: Houdini – A new way to test web apps by gre on Wednesday January 15, 2014 @05:53PM (#7066818)

The video demonstrates how we would like the user-assisted side of it to work. For reasons like you mention, it might require more than DOM inspection in the end. What if tweets are supposed to show in the feed four times instead of once? To achieve the right level of control I think it needs API access to the database. We are close but not completely there yet. Thanks for the feedback!

[ Parent | on HN ]

Re:Show HN: Houdini – A new way to test web apps by rogerdickey on Wednesday January 15, 2014 @04:51PM (#7066442)

one approach is to look at the progressive diff between the insert tests & verify that the DOM is changing in the same incremental way

[ Parent | on HN ]

Re:Show HN: Houdini – A new way to test web apps by aantix on Wednesday January 15, 2014 @05:09PM (#7066534)

That was my point; a "progressive diff" isn't just two samples. At test sample #2, whether an item inserts or updates, either could be correct at that point.

[ Parent | on HN ]