[Commotion-dev] Automating Browser Testing

Ben West ben at gowasabi.net
Thu Apr 17 11:36:28 EDT 2014


If you are willing to isolate some portions of the commotion-router web UI
for browser compatibility testing, i.e. not do such tests exclusively on
target hardware, you could try running an instance of uhttpd/luci/etc
compiled for x86 (or likewise running the same under an virtualized
environment via VMWare Player / VirtualBox).

Jenkins is quite flexible in letting you specify post-build scripts to do
pretty much anything that can be scripted.  For example, deploy a freshly
compiled VMDK file to a VMWare Player instance, or simply copy over the
updated contents of /www/luci-static and /usr/lib/lua over to the instance
of uhttpd/luci you have running on whatever port on the build server, and
then point automated browser testing at that.

This would require modifying / extracting pieces from commotion-router to
run meaningfully enough for testing purposes in an environment w/o a radio.


On Thu, Apr 17, 2014 at 9:50 AM, Andrew Reynolds <
andrew at opentechinstitute.org> wrote:

> I spent some time with the IDE this week and am just starting to work
> with the perl and python bindings. So far it seems like exactly what I'm
> looking for.
>
> The biggest hurdle I see right now is that we can't run the
> commotion-router web interface on the build server (at least not live),
> so we may not be able to integrate fully with jenkins. If there's a
> solution I'm overlooking I would love to hear it.
>
> -andrew
>
> On 04/10/2014 11:55 AM, Bill Comisky wrote:
> > My 2 cents: I've been using Selenium for a few years through the perl
> > bindings, and have been pretty happy with it.   The Selenium IDE plugin
> for
> > firefox makes it pretty easy to construct the selectors for your browser
> > actions.  I've used it primarily with firefox, so can't speak to
> > cross-browser testing.
> >
> > Bill
> >
> >
> > On Thu, Apr 10, 2014 at 11:27 AM, Andrew Reynolds <
> > andrew at opentechinstitute.org> wrote:
> >
> >> Hi all,
> >>
> >> We're doing a lot of manual testing for our Commotion releases these
> >> days, including a lot of browser-based tests of the luci interfaces. For
> >> example, we check all fields for proper input validation, make sure file
> >> upload widgets work, check all the links, etc.
> >>
> >> I've been looking at Selenium to try to automate some of the work. It
> >> seems popular and integrates with Jenkins but I've never actually used
> it.
> >>
> >> Have any of you used Selenium or similar products enough to favor one or
> >> the other?
> >>
> >> -andrew
> >>
> >>
> >> _______________________________________________
> >> Commotion-dev mailing list
> >> Commotion-dev at lists.chambana.net
> >> https://lists.chambana.net/mailman/listinfo/commotion-dev
> >>
> >>
> >
>
>
>
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
>
>


-- 
Ben West
http://gowasabi.net
ben at gowasabi.net
314-246-9434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20140417/cda64d88/attachment-0001.html>


More information about the Commotion-dev mailing list