What test framework were you using before? I just started using SeleniumRC and have found it to be pretty good, although they could use some more functionality around AJAX testing, but it wouldn't need much... and it's already open-source, so I am just curious which are the problems you couldn't solve that caused you to branch out with your own testing framework?
Thanks! Alan
Roy Russo
· 1 year ago
Will this allow for testing of all page elements, or is it limited to JS? In other words... does it work like Grinder and Selenium?
Jeff Haynie
· 1 year ago
@alan - selenium is a good product. if you use selenium you should consider the open source push to test stuff as well. we're just going to be doing some things that are different - in some cases maybe it will overlap, in some cases it will be very complementary.
@roy - yeah, it's not just for testing JS and in fact, it's really primarily designed for testing out the UI (like HTML, etc).
Todd Ditchendorf
· 1 year ago
I'm very excited to see this Jeff... I've used Selenium before and it's excellent... but I really think there's a lot of room for more automated web testing tools. Lots of web UI/JS/HTML/CSS stuff is still very difficult (impossible?) to test in an automated fashion. Go TestMonkey!
One suggestion: I know it matches the old JUnit convention, but I wish the comment string parameter were the final param rather than the first... especially in JS, it seems nice to have optional params at the end. I know some think that the comment param should not be optional, but reasonable people will disagree on that... at least putting it last lets users follow their own preference there...
Really looking forward to watching this! Great job!
Jeff Haynie
· 1 year ago
@itod -- thanks. i like the idea of putting it at the end, will make that optional. we can also just basically check and see if the first param is typeof object and assume it's not provided too....
Andy
· 1 year ago
I got to see this in Chicago. Pretty good stuff. I'm kind of tired of JUnit+HttpClient
matt
· 1 year ago
I took a spin through the code on GitHub - looks great - quick question - automation...I'm missing the big picture here - how would I plug this into my CI build? Will there be any notion of "autodiscovery" of tests so that you don't need to manually update a manifest of test suites every time something is added? That aside - this is phenomenal - thanks for making this available!
Jeff Haynie
· 1 year ago
@matt - thanks. we don't have the CI build pieces in yet but they will overlay and we should have something in place for that soon. we have a lot of additional automation capabilities we're going to be introducing soon....
All Comments
Thanks!
Alan
@roy - yeah, it's not just for testing JS and in fact, it's really primarily designed for testing out the UI (like HTML, etc).
One suggestion: I know it matches the old JUnit convention, but I wish the comment string parameter were the final param rather than the first... especially in JS, it seems nice to have optional params at the end. I know some think that the comment param should not be optional, but reasonable people will disagree on that... at least putting it last lets users follow their own preference there...
Really looking forward to watching this! Great job!
Nicely done. I'm looking forward to support it.
-Frank