W3C home > Mailing lists > Public > public-mwts@w3.org > April 2007

Re: Progress on test harness

From: Allen Wang <Xiaozhong.Wang@Sun.COM>
Date: Mon, 09 Apr 2007 15:10:37 -0700
To: Dominique Hazael-Massieux <dom@w3.org>
Cc: public-mwts@w3.org
Message-id: <461AB9DD.1070104@sun.com>


Here are my thoughts about implementing sessions.

We need to associate an ID with each session. It should not be the 
native session ID on the server side, but a randomly generated 10 digit 
number. Let's assume it is called TestSessionID. On server side, the 
TestSessionID can be stored in $_SESSION array in PHP during an active 
session and into the database for permanent storage. On client side, we 
use two approaches:

- Using cookie.

I don't know whether it is typical that a mobile browser will support a 
cookie. But we can use it as the default approach and try to set and get 
cookie with the name TestSessionID and the value being the generated 10 
digit number.

- If cookie is not supported, we give the user the TestSessionID and ask 
him/her to store it for later use. We can also send the TestSessionID to 
the user if an email address is provided.

I imagine the basic session related control flow is like this:

- When a user accesses the start page of a test suite, we ask whether 
he/she wants a new test session or restore a session.

- If a new session is started, we can add an extra step to detect 
whether cookie is supported in the user agent's browser by setting and 
retrieving the TestSessionID through a cookie. If the retrieved value is 
not set, cookie is not supported and we provide the TestSessionID to the 

- If user is restoring a session, we can try to retrieve the 
TestSessionID from the cookie. If not set, cookie is not supported and 
we need to ask the user to input the TestSessionID. Either way, we get 
the TestSessionID and restores the test session from the database.

Of course, the other piece of work will be storing the test result for 
each test with associated TestSessionID.


Dominique Hazael-Massieux wrote:
> Hi,
> A few progress to report on the test harness:
>  * the list of test cases is now taken from the database, rather than
> hardcoded in the script
>  * I've made it possible to associate specific HTTP headers with a given
> test case in the process; this was already needed for one test suite I
> wanted to integrate in the harness
>  * the SVG Tiny test suite is now available through the harness:
> http://www.w3.org/2007/03/mth/harness ; I wonder if I should also
> include SVG Basic; none of my mobile devices has SVG support, so I
> haven't recorded any useful results at this time.
>  * at each step you have now indications of where you are in the test
> suite
> I haven't implemented the session id concept yet, nor its related
> features.
> I'm also trying to figure out whether I can include the OMA Test suites
> in that harness within their licensing terms.
> As a reminder, the results table are linked from:
> http://www.w3.org/2007/03/mth/results
> Dom
Received on Monday, 9 April 2007 22:07:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:08:01 UTC