CVS log for 2002/ws/desc/test-suite/results-messages/Message-tests-results.html

Request diff between arbitrary revisions

updated Canon results: lists.w3.org/Archives/Public/www-ws-desc/2007Apr/0004.html

New Canon logs: http://lists.w3.org/Archives/Public/www-ws-desc/2007Mar/0080.html

Updated the testsuite to the new namespaces.

New logs. Regenerated results.

Incorporated 3/14-15 results

Fixed a few characters in httpLocationTable.xml re LocationTemplate-2G

Updated WSO2 results for LocationTemplate 2-G.  Updated expected results and testcase.

New results from Canon: http://lists.w3.org/Archives/Public/www-ws-desc/2007Feb/0208.html
Fiddled with the baselines a little bit too.

New results from Canon: http://lists.w3.org/Archives/Public/www-ws-desc/2007Feb/0208.html
Fiddled with the baselines a little bit too.

Omit Content-Type assertions when http:method="GET" or "PUT".

Added assertion verifying that SOAP Action is ignored when used with the SOAP Response MEP.

New results:
http://lists.w3.org/Archives/Public/www-ws-desc/2007Feb/0146.html
http://lists.w3.org/Archives/Public/www-ws-desc/2007Feb/0150.html
http://lists.w3.org/Archives/Public/www-ws-desc/2007Feb/0152.html

Fixed LocationTemplate-1G expected template (* should not be %-encoded).

Fixed multipart/form-data assertions - checks for text in the body rather than XML (no specific assertions within that text though.)

Fixed Content-Encoding assertions on faults.

Added alternate HTTP Locations to the httpLocationsTable.xml, and updated stylesheets to process them.  This accomodates changes in serialization of typed data (e.g. canonicalization is OK).

Fixed LocationTemplate-2G, MessageTest-3G, added new WSO2 results, regenerated all results.

Per CR 143:
- change transferCoding to contentEncoding in the interchange format schemas
- similarly change the testcases (MessageTest-1G, 3G, 4G)
- similarly change the message-level assertion stylesheets
- update wsdl-xslt accordingly
- change MessageTest-1G so that it doesn't rely on gzip encoding support (EchoString operation now has contentEncoding="".

regenerated all results.

Added LocationTemplate-2G and 3G, updated expected values on LocationTemplate-1G per CR117 resolution.

Clean build (missing some logs.)

New results from Canon->WSO2, ModuleComposition-1G, MessageTest-6G.

New canon->wso2 results.

Updated with new WSO2 logs: http://lists.w3.org/Archives/Public/www-ws-desc/2007Jan/0190.html, http://lists.w3.org/Archives/Public/www-ws-desc/2007Jan/0193.html, plus new Canon interchange results.

Added MessageMultipart test results

More results: http://lists.w3.org/Archives/Public/www-ws-desc/2007Jan/0182.html

More results: http://lists.w3.org/Archives/Public/www-ws-desc/2007Jan/0180.html

Regenerated results (new Canon, Woden)

Regenerated all results (including test coverage, validation, etc.)

Possibly missing intermediate results files...

New

New logs

See http://lists.w3.org/Archives/Public/www-ws-desc/2007Jan/0136.html

1)      Removed GenericSOAPBinding from MessageTest-1G, including the
endpoint referring to it.

2)      Created MessageTest-6G that only has the GenericSOAPBinding,
including removing endpoints associated with other bindings.

3)      Changed the content models of Send and GuaranteedFault to elements
sendString and sendInt, with xs:string and xs:int types repectively.

4)      Changed the name of the Service, changed some comments

+ Regenerated all results.

Back out previous change, except for:

Giving the services used for message tests unique service names
Making sure query parameter separator is consistent with explicit params

See http://lists.w3.org/Archives/Public/www-ws-desc/2007Jan/0122.html:

In order not to lose the few bindings that make sense under SOAP, I’ve cloned LocationTemplate-1G into LocationTemplate-2G which is an HTTP binding-only version.  I twiddled a few other details to keep everything sufficiently unique (e.g. service name, whttp:location URLs, etc.)

I’ve cut the AutoRemainder, AdditionalQueryParams, and AutoQueryParams bindings from LocationTemplate-1G.

Since we’ve clarified that the {http location} is engaged on both soap-request and request-response MEPs, I cloned the remaining 4 operations and test them on the request-response MEP as well.

While doing this, I noticed some service names were not unique within the whole set of tests we’re doing, which is inconvenient for some implementations like Axis2.  I updated MessageTest-2G,3G,4G service names (which should affect the component model more than the message tests.)

Also made sure queryParameterSeparater values were consistent with any query params explicitly specified in whttp:location.

Removed assertion about status code when soapFaultCode = #any.
Regenerated results.

Added WSO2 results.
Fixed columnar display of multiple vendor's results.

Regenerated results.
Updated dashboard with more explanatory text.

Renamed log files to static names (CVS will take care of the dates).
Changed MessageTest-2G expected data in httpLocationTable to myfirst, mymiddle, mylast.
Rebuilt results.

Added {http location} support - now assertions go through httpLocationsTable.xml for replacement of URLs with the post-template-resolution value.

Added Canon results.
Updated ws-i.xslt to accomodate application/xml and application/x-www-url-formencoded types.
Fixed multiple table headers in summary in message-tests-results.xsl.
Fixed run-on xpath in generate-xpath-assertions.xslt.

Added generated link from individual test results directly to the point in the log where the message is.
When there is more than one <outfault>, the logger assumes the first one will be thrown (on *Fault operations).
Regenerated results over exisiting logs.

Added rollup of Message Exchange Test results.