Re: [widgets] Widget Updates tests?
Scott Wilson wrote:
Just one more thing...
Test ta-processing2-14, Tests that update-info element's src attribute need to be
valid, else it is ignored. The widget is not updated or replaced.
However, the value to fail with is fail.wgt which ought to be interpreted as
a relative URL, in which case the expected result would be to turn this into:
http://people.opera.com/harig/wupdres/resources/fail.wgt
Which is valid.
So, the test needs to have a different value to be an invalid src attribute.
Missed this one - it has been fixed and the src attribute has been set
to an invalid IRI (':') as required.
- Rich
Re: [widgets] Widget Updates tests?
Scott Wilson wrote: Right, I've done some basic work on the tests in Apache Wookie - most of them seem to work OK so far; I need to do interactive testing next - I've tested processing the update element in config.xml and acquiring and validating the UDD, but not actually processing the updates. However there are some issues I've found so far: Test ta-preparation1-8 This fails to parse as a valid widget as the XML isn't well-formed Test ta-processing2-3 I get a content type of text/html when getting the UDD Test ta-processing2-7 I get an error of the UDD XML not being well-formed Test ta-processing2-9 I get a content type of text/html when getting the UDD All the above tests have been fixed. Test ta-processing2-16 We throw a UDD parse exception when a UDD has a relative URL for the src attribute, but the test seems to assume you just silently fail to update the widget? The processing in this case was underspecified in the spec. I've updated the specification to allow for relative URLs to be included in the 'src' attribute. The resolution system for relative URL src attributes to absolute valid IRIs has also been included in the spec (i.e. resolve relative URLs relative to the UDDs IRI). Relative URLs are not allowed in the update-description element of a widget's config.xml. We've therefore replaced ta-processing2-16 test with a test to check that the resolution of src attribute relative URLs is working correctly. Test ta-processing2-19 I get a content type of text/html when getting the UDD Test ta-processing2-20 I get a content type of text/html when getting the UDD These tests have been fixed. HTH, Rich
Re: [widgets] Widget Updates tests?
On 28 Apr 2011, at 12:19, Rich Tibbett wrote: Scott Wilson wrote: Right, I've done some basic work on the tests in Apache Wookie - most of them seem to work OK so far; I need to do interactive testing next - I've tested processing the update element in config.xml and acquiring and validating the UDD, but not actually processing the updates. However there are some issues I've found so far: Test ta-preparation1-8 This fails to parse as a valid widget as the XML isn't well-formed Test ta-processing2-3 I get a content type of text/html when getting the UDD Test ta-processing2-7 I get an error of the UDD XML not being well-formed Test ta-processing2-9 I get a content type of text/html when getting the UDD All the above tests have been fixed. Great, thanks! Test ta-processing2-16 We throw a UDD parse exception when a UDD has a relative URL for the src attribute, but the test seems to assume you just silently fail to update the widget? The processing in this case was underspecified in the spec. I've updated the specification to allow for relative URLs to be included in the 'src' attribute. The resolution system for relative URL src attributes to absolute valid IRIs has also been included in the spec (i.e. resolve relative URLs relative to the UDDs IRI). Relative URLs are not allowed in the update-description element of a widget's config.xml. We've therefore replaced ta-processing2-16 test with a test to check that the resolution of src attribute relative URLs is working correctly. Makes sense. Test ta-processing2-19 I get a content type of text/html when getting the UDD Test ta-processing2-20 I get a content type of text/html when getting the UDD These tests have been fixed. HTH, Rich Its a big help, thanks. One more thing, the widget at: http://people.opera.com/harig/wupdres/resources/pass.wgt ... isn't valid as its not well formed - there should be ? at end of line 1. S
Re: [widgets] Widget Updates tests?
On Thu, 28 Apr 2011 14:57:20 +0200, Scott Wilson scott.bradley.wil...@gmail.com wrote: One more thing, the widget at: http://people.opera.com/harig/wupdres/resources/pass.wgt ... isn't valid as its not well formed - there should be ? at end of line 1. Fixed. -- Hari Kumar G Quality Assurance Opera Software
Re: [widgets] Widget Updates tests?
On 28 Apr 2011, at 14:11, Hari Kumar G wrote: On Thu, 28 Apr 2011 14:57:20 +0200, Scott Wilson scott.bradley.wil...@gmail.com wrote: ... One more thing, the widget at: http://people.opera.com/harig/wupdres/resources/pass.wgt ... isn't valid as its not well formed - there should be ? at end of line 1. Fixed. Fantastic - thanks. Just one more thing... Test ta-processing2-14, Tests that update-info element's src attribute need to be valid, else it is ignored. The widget is not updated or replaced. However, the value to fail with is fail.wgt which ought to be interpreted as a relative URL, in which case the expected result would be to turn this into: http://people.opera.com/harig/wupdres/resources/fail.wgt Which is valid. So, the test needs to have a different value to be an invalid src attribute. S -- Hari Kumar G Quality Assurance Opera Software
Re: [widgets] Widget Updates tests?
Arthur Barstow wrote: Thanks for the update Richard. Is this spec ready for LCWD publication? If not, what remains to be done before it is LC-ready? Opera is happy for this specification to proceed to LCWD. I believe Marcos wanted to take a pass over the spec so I'll leave him to inform the group on those plans. Marcos, if we aim for LCWD in 2-3 weeks will that be OK? Also, I would appreciate any implementation data you can share so we can update [1] I've updated the wiki with a placeholder for Widget Updates. At Opera we've implemented this specification for Opera Extensions. We'll be uploading Opera's test results shortly. Since the bulk of the specification is relatively new (~6 months), Opera Widget Updates do not currently implement this specification but use a proprietary update mechanism. If others have any implementation support to add I hope they will let us know so we can improve the spec as required. Thanks, Rich [1] http://www.w3.org/2008/webapps/wiki/WidgetImplementation
Re: [widgets] Widget Updates tests?
On 26 Apr 2011, at 16:59, Rich Tibbett wrote: Hi Scott, On 28.03.2011 at 15:59, Scott Wilson wrote: Are there any tests available - even informal ones - for the Widget Updates[1] spec? We've just uploaded the Widget Updates test suite to the CVS repository. The Widgets Updates test suite is available here: http://dev.w3.org/2006/waf/widgets-updates/test-suite/ Individual test cases are available at http://dev.w3.org/2006/waf/widgets-updates/test-suite/test-cases/ Once we have some implementer feedback on the tests we'll go ahead and populate the Widget Updates implementation report in the usual way: http://dev.w3.org/2006/waf/widgets-updates/imp-report/ If you have any feedback or questions just let us know. Thanks Rich! I'll get to work on the Widget Updates implementation in Apache Wookie now :-) - Rich [1] http://www.w3.org/TR/widgets-updates/
Re: [widgets] Widget Updates tests?
Right, I've done some basic work on the tests in Apache Wookie - most of them seem to work OK so far; I need to do interactive testing next - I've tested processing the update element in config.xml and acquiring and validating the UDD, but not actually processing the updates. However there are some issues I've found so far: Test ta-preparation1-8 This fails to parse as a valid widget as the XML isn't well-formed Test ta-processing2-3 I get a content type of text/html when getting the UDD Test ta-processing2-7 I get an error of the UDD XML not being well-formed Test ta-processing2-9 I get a content type of text/html when getting the UDD Test ta-processing2-16 We throw a UDD parse exception when a UDD has a relative URL for the src attribute, but the test seems to assume you just silently fail to update the widget? Test ta-processing2-19 I get a content type of text/html when getting the UDD Test ta-processing2-20 I get a content type of text/html when getting the UDD S On 26 Apr 2011, at 16:59, Rich Tibbett wrote: Hi Scott, On 28.03.2011 at 15:59, Scott Wilson wrote: Are there any tests available - even informal ones - for the Widget Updates[1] spec? We've just uploaded the Widget Updates test suite to the CVS repository. The Widgets Updates test suite is available here: http://dev.w3.org/2006/waf/widgets-updates/test-suite/ Individual test cases are available at http://dev.w3.org/2006/waf/widgets-updates/test-suite/test-cases/ Once we have some implementer feedback on the tests we'll go ahead and populate the Widget Updates implementation report in the usual way: http://dev.w3.org/2006/waf/widgets-updates/imp-report/ If you have any feedback or questions just let us know. - Rich [1] http://www.w3.org/TR/widgets-updates/
Re: [widgets] Widget Updates tests?
On Mon, Mar 28, 2011 at 3:59 PM, Scott Wilson scott.bradley.wil...@gmail.com wrote: Hi everyone, Are there any tests available - even informal ones - for the Widget Updates[1] spec? None yet :( -- Marcos Caceres http://datadriven.com.au
Re: [widgets] Widget Updates tests?
Thanks for the update Richard. Is this spec ready for LCWD publication? If not, what remains to be done before it is LC-ready? Also, I would appreciate any implementation data you can share so we can update [1] -Thanks, AB [1] http://www.w3.org/2008/webapps/wiki/WidgetImplementation On Apr/26/2011 11:59 AM, ext Rich Tibbett wrote: Hi Scott, On 28.03.2011 at 15:59, Scott Wilson wrote: Are there any tests available - even informal ones - for the Widget Updates[1] spec? We've just uploaded the Widget Updates test suite to the CVS repository. The Widgets Updates test suite is available here: http://dev.w3.org/2006/waf/widgets-updates/test-suite/ Individual test cases are available at http://dev.w3.org/2006/waf/widgets-updates/test-suite/test-cases/ Once we have some implementer feedback on the tests we'll go ahead and populate the Widget Updates implementation report in the usual way: http://dev.w3.org/2006/waf/widgets-updates/imp-report/ If you have any feedback or questions just let us know. - Rich [1] http://www.w3.org/TR/widgets-updates/
