W3C home > Mailing lists > Public > public-media-fragment@w3.org > May 2010

Test Cases: moving forward

From: RaphaŽl Troncy <raphael.troncy@cwi.nl>
Date: Wed, 19 May 2010 11:03:37 +0200
Message-ID: <4BF3A969.8070507@cwi.nl>
To: Media Fragment <public-media-fragment@w3.org>
Hi Silvia, all,

I think we have now a very solid base with the test cases resolution 
described at 

I have some minor comments:
   - For #02: originally, we had two test cases to test: #t=0,0 and 
#t=a,a where a>0. Silvia has merged them into a single one, which makes 
sense but I wonder if we should not split them again in order to have 
explicit test cases for the boundary case!
   - For #10: this can happen only if s > 0 and the entire fragment 
requested is before the start position of the media. We could add this 
in comment ?
   - For #12: you don't want to say in comment that this is equivalent 
to #t=s,e ?
   - For #11, #12, #14 and #16: I suggest we force a 206 answer, with 
the rationale that a fragment has been requested (that might be equal to 
the entire resource but this is similar to case #01!).

In the sub-section "Temporal dimension syntax", should we have more test 
cases when the unit is %-encoded? Currently, we have only one for the 
'n' of 'npt', but what about the 's' for 'smpte', etc. ? This could lead 
to a very big number of ugly test cases :-(

What to do next? Should we have someone (Jack?) to review them ? Should
we put the test cases in the spec or in a separate document ?
The Spatial dimension is easy, there will be no test cases, no request 
is issued.
What about the Trach dimension test cases ?


RaphaŽl Troncy
EURECOM, Multimedia Communications Department
2229, route des CrÍtes, 06560 Sophia Antipolis, France.
e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200
Web: http://www.eurecom.fr/~troncy/
Received on Wednesday, 19 May 2010 09:05:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:44 UTC