Major "thank you" for doing github login without requiring me to hand over my private repositories.
Show HN: Houdini – A new way to test web apps
11–20 of 24 posts
Re: Show HN: Houdini – A new way to test web apps
#12In 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?
Re: Show HN: Houdini – A new way to test web apps
#13Major "thank you" for doing github login without requiring me to hand over my private repositories.
Thanks for the feedback! Definitely trying to be reasonable :) Definitely welcome any other suggestions!
Re: Show HN: Houdini – A new way to test web apps
#14This looks awesome. Scared to put the Javascript on my site though, because it's unclear to me how the embedded Javascript will be able to differentiate me (the site owner) from regular users.
I don't want regular users seeing the "1 test generated" thing on each page. Maybe clarify this a little on the page where you give me the Javascript snippet.
Re: Show HN: Houdini – A new way to test web apps
#15In 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 u…
one approach is to look at the progressive diff between the insert tests & verify that the DOM is changing in the same incremental way
Re: Show HN: Houdini – A new way to test web apps
#16This looks awesome. Scared to put the Javascript on my site though, because it's unclear to me how the embedded Javascript will be able to differentiate me (the site owner) from regular users. I don't want regular users seeing the "1 test generated" thing on each page. Maybe clarify this a little on the page where you give me the Javascript snippet.
Will definitely clarify this on the dashboard. Users of the site won't see those notifications for sure. Those are configurable and you'd only use those on your dev environments.
Re: Show HN: Houdini – A new way to test web apps
#17In 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 u…
one approach is to look at the progressive diff between the insert tests & verify that the DOM is changing in the same incremental way
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.
Re: Show HN: Houdini – A new way to test web apps
#18Re: Show HN: Houdini – A new way to test web apps
#19Would be recommending this to the QA folks at work. Thanks for sharing!
Re: Show HN: Houdini – A new way to test web apps
#20Very cool. I recently had an idea along those lines. Good to see someone's building something in this area. Will it be possible to generate CasperJS- or Selenium-compatible test scripts from Houdini so tests can be run in a CI environment, too?