Unit testing via a browser
Page: 1
Recent posts in this topic
ryan.doherty
on Feb 8. 2007. 8:39 pm
I see that activeCollab has unit tests, which is very good. I am curious if it has anything that would test DHTML and AJAX functionality. I ask this because I know activeCollab is heading in this direction and simple unit tests in the framework can't test that.
I'm using WATIR (http://wtr.rubyforge.org/) right now and it's pretty damn good. Basically you 'drive' IE with Ruby and it behaves as if a real person was filling out forms, clicking on links, verifying results and that elements exist in the DOM, just about anything a real user could do.
Thoughts?
I'm using WATIR (http://wtr.rubyforge.org/) right now and it's pretty damn good. Basically you 'drive' IE with Ruby and it behaves as if a real person was filling out forms, clicking on links, verifying results and that elements exist in the DOM, just about anything a real user could do.
Thoughts?
Staff
Ilija Studen
on Feb 8. 2007. 9:12 pm
SimpleTest (test framework that I use) has a nice little browser implementation. Nothing fancy (no JS support), but enough to test some basic behavior. Still, open issue is what to use for JS testing.
I develop on a Mac so anything IE specific will not work. I've read on your blog that Watir developers plan to introduce support for Firefox. Than I'll give it a try.
Any other resources for JS testing? Just curious.
I develop on a Mac so anything IE specific will not work. I've read on your blog that Watir developers plan to introduce support for Firefox. Than I'll give it a try.
Any other resources for JS testing? Just curious.
activeCollab team member | LinkedIn
ryan.doherty
on Feb 8. 2007. 11:19 pm
Interesting, so is it actually running a web browser or just mimicking the GET and POST actions of a browser? From the documentation, I'm guessing it's creating a DOM tree in PHP and parsing that to get forms, images, links, etc.
That's cool you're developing on a Mac, but activeCollab should be tested in IE, FF and Opera on Windows anyway. You could use Parallels, I've seen it, works very well. Does cost money though, but it's one of those programs that I want to pay for because it's so good.
Firewatir looks like it's stable: http://code.google.com/p/firewatir/wiki/Firewatir . I haven't used it though.
This could become difficult if we will need to test on all 'modern' browsers. I see you are using the YUI library, which is good, provides an abstraction layer.
I'm all for FireWATIR or just WATIR testing, especially if activeCollab is going to have more JS/AJAX interactivity. There are other testing suites out there, Silk is the only one that comes to mind. I really like Watir though because I love Ruby.
That's cool you're developing on a Mac, but activeCollab should be tested in IE, FF and Opera on Windows anyway. You could use Parallels, I've seen it, works very well. Does cost money though, but it's one of those programs that I want to pay for because it's so good.
Firewatir looks like it's stable: http://code.google.com/p/firewatir/wiki/Firewatir . I haven't used it though.
This could become difficult if we will need to test on all 'modern' browsers. I see you are using the YUI library, which is good, provides an abstraction layer.
I'm all for FireWATIR or just WATIR testing, especially if activeCollab is going to have more JS/AJAX interactivity. There are other testing suites out there, Silk is the only one that comes to mind. I really like Watir though because I love Ruby.
Staff
Ilija Studen
on Feb 9. 2007. 11:27 am
H Ryan,
I didn't know about FireWATIR. Looks pretty nice. Important thing about tests is that it need to be run easily and quickly and if that involves firing up a virtual machine, starting Windows and running Ruby and IE under it it does not really qualify as easy and quick. That was the main reason why I pointed out that my development platform is a Mac...
As far as I can see, FireWATIR tests are compatible with WATIR tests so they can be ran against both browsers? That is something that can be handy :)
Thanks for the suggestions!
Btw, SimpleBrowser class in SimpleTest does not interact with the browser as far as I know.
I didn't know about FireWATIR. Looks pretty nice. Important thing about tests is that it need to be run easily and quickly and if that involves firing up a virtual machine, starting Windows and running Ruby and IE under it it does not really qualify as easy and quick. That was the main reason why I pointed out that my development platform is a Mac...
As far as I can see, FireWATIR tests are compatible with WATIR tests so they can be ran against both browsers? That is something that can be handy :)
Thanks for the suggestions!
Btw, SimpleBrowser class in SimpleTest does not interact with the browser as far as I know.
activeCollab team member | LinkedIn
ryan.doherty
on Feb 9. 2007. 6:13 pm
Yeah, FireWATIR tests are supposed to be compatible with WATIR tests. I haven't heard of anyone really complaining, so I think it works.
It would be cool to have the tests run on both browsers.
BTW, how do you test for IE? I poked around my install of activeCollab with IE and everything looks fine, no CSS problems.
It would be cool to have the tests run on both browsers.
BTW, how do you test for IE? I poked around my install of activeCollab with IE and everything looks fine, no CSS problems.
Staff
Ilija Studen
on Feb 9. 2007. 8:17 pm
Most of the layout was done on PC because I switched to Mac just recently (in December). I kept my PC box for testing.
I'll play with FireWATIR when we get to functional tests part of the development (interface is ready and we need to check the interaction through browser). Thanks for the recommendations a lot! It solves one pretty big problem (interface testing).
I'll play with FireWATIR when we get to functional tests part of the development (interface is ready and we need to check the interaction through browser). Thanks for the recommendations a lot! It solves one pretty big problem (interface testing).
activeCollab team member | LinkedIn
Topic is locked. If you have something important to say about issues discussed on this page please write at hi@a51dev.com.
