Mobile Web Test Suites Working Group blog http://www.w3.org/2005/MWI/Tests/blog en-EU hourly 1 2000-01-01T12:00+00:00 Automated testing of a browser engine http://www.w3.org/2005/MWI/Tests/blog/2009/11/10/automated_testing_of_a_browser_engine 2009-11-10T14:56:06Z Wilhelm Joys Andersen Announcements “The cornerstone of all testing done on the core of the Opera browser is our automated regression testing system, named SPARTAN. The system consists of a central server and about 50 test machines running our 120 000 automated tests on all core reference builds. The purpose of this system is to help us discover any new bugs we introduce as early as possible, so that we can fix them before they cause any trouble for our users.” Read more on the Core Concerns blog.

“The cornerstone of all testing done on the core of the Opera browser is our automated regression testing system, named SPARTAN. The system consists of a central server and about 50 test machines running our 120 000 automated tests on all core reference builds. The purpose of this system is to help us discover any new bugs we introduce as early as possible, so that we can fix them before they cause any trouble for our users.”

Read more on the Core Concerns blog.

]]> Test Workshop concluded successfully http://www.w3.org/2005/MWI/Tests/blog/2009/09/29/test_workshop_concluded_successfully 2009-09-29T15:34:09Z Kai Hendry Announcements The first Test Workshop has concluded as a productive face-to-face meeting. Work is now focusing on testing Widget Digital signature support in widget runtimes and further review. Your comments are very welcome. Widget runtime implementors are encouraged to take a look at http://dev.w3.org/2006/waf/widgets/tests/test-suite.xml as it may help them implement an interoperable W3C widget runtime. W3C test workshop participants

The first Test Workshop has concluded as a productive face-to-face meeting.

Work is now focusing on testing Widget Digital signature support in widget runtimes and further review. Your comments are very welcome.

Widget runtime implementors are encouraged to take a look at http://dev.w3.org/2006/waf/widgets/tests/test-suite.xml as it may help them implement an interoperable W3C widget runtime.

]]> Preparing for the Widget Test Cases Creation Event http://www.w3.org/2005/MWI/Tests/blog/2009/09/07/preparing_widget_test_event 2009-09-07T14:34:40Z Kai Hendry Announcements The test case creation meeting agenda & logistics now have a home at the Test Workshop 2009 wiki. A list of test assertions should become the reference point for our face-to-face meeting in Germany. Recently we have some created some scripts for generating Widget digital signatures. The meeting will be very "hands on", so please make sure you are comfortable using zip and editing the configuration document. See you in two weeks! Düsseldorf

The test case creation meeting agenda & logistics now have a home at the Test Workshop 2009 wiki.

A list of test assertions should become the reference point for our face-to-face meeting in Germany.

Recently we have some created some scripts for generating Widget digital signatures. The meeting will be very "hands on", so please make sure you are comfortable using zip and editing the configuration document.

See you in two weeks!

]]> Widget Test Cases Creation Event http://www.w3.org/2005/MWI/Tests/blog/2009/07/29/widget_test_event 2009-07-29T09:39:52Z Kai Hendry Announcements In order to help ensure interoperable W3C Widget runtimes, Vodafone are kindly hosting the first ever W3C Widget test cases creation event. The dates are set for the 2009-09-21 (Monday) till 2009-09-23 (Wednesday) and the venue will be in Düsseldorf in Western Germany. Interested in Web Widgets? Tired of fragmentation? Able to write some tests? Please join us by registering for the event. The aim is to complete the Widget test suite. Once registering to prepare for the event, please review the test plan and existing tests. A contribution guide and event details will follow soon. In order to help ensure interoperable W3C Widget runtimes, Vodafone are kindly hosting the first ever W3C Widget test cases creation event. The dates are set for the 2009-09-21 (Monday) till 2009-09-23 (Wednesday) and the venue will be in Düsseldorf in Western Germany.

Interested in Web Widgets? Tired of fragmentation? Able to write some tests? Please join us by registering for the event.

The aim is to complete the Widget test suite. Once registering to prepare for the event, please review the test plan and existing tests. A contribution guide and event details will follow soon.

]]> Memory test for mobile browsers http://www.w3.org/2005/MWI/Tests/blog/2009/06/01/memory_test_for_mobile_browsers 2009-06-01T08:37:22Z Dominique Hazael-Massieux Announcements A few months ago, we looked at how well existing performance test suites worked on mobile browsers: they generally worked poorly (if at all), and in many occasions, the limiting factor was the memory required to run these tests. As a follow-up, we have developed a simple test (source code) that allows to determine the maximum amount of memory a browser can dispose of. The test is interactive and with every successful pass, it prompts the user to increase the size of data put in memory until an upper limit of 100 MB JSON's . If the browser fails to fetch a given amount of data, the user can pick a lower target. Depending on how the device is managing out-of-memory errors, it may be more or less difficult to find that upper limit, but overall, it should help get a fairly good idea of the memory limitations of a given browser/device pair. The Mobile Test working group welcome your comments. Any comments and/or suggestions can be sent to public mailing list or on this blog. A few months ago, we looked at how well existing performance test suites worked on mobile browsers: they generally worked poorly (if at all), and in many occasions, the limiting factor was the memory required to run these tests.

As a follow-up, we have developed a simple test (source code) that allows to determine the maximum amount of memory a browser can dispose of.

The test is interactive and with every successful pass, it prompts the user to increase the size of data put in memory until an upper limit of 100 MB JSON's . If the browser fails to fetch a given amount of data, the user can pick a lower target.

Depending on how the device is managing out-of-memory errors, it may be more or less difficult to find that upper limit, but overall, it should help get a fairly good idea of the memory limitations of a given browser/device pair.

The Mobile Test working group welcome your comments. Any comments and/or suggestions can be sent to public mailing list or on this blog.

]]>