[OpenID] Backwards Compatibility

[Brett McDowell]

In the spirit of trying to leverage/re-use any capacity and/or  
lessoned learned in the area of interoperability & conformance "test  
suit" development and program administration, I have some questions  
about what is really needed in this regard right now (depending on the  
answer, maybe I could offer some help).

Which of the following testing methodologies sounds like the most  
useful at this point in time?
(a) Reference Implementation to test against
(b) Conformance test suite with logging, verbose error handling and  
reporting, etc.
(c) Just a test procedures document that clearly lays out  
interoperability testing per conformance "mode"
(d) Online coordination support for voluntary testing using (c) from  
above
(e) In-person interop testing events based on (c) above

And related to this, is there any need/demand for 3rd-party proctored  
interoperability testing & certification of OpenID implementations, or  
is all we need/want right now more support for voluntary/informal  
testing?


Brett McDowell | +1.413.652.1248 | http://info.brettmcdowell.com

On Mar 17, 2009, at 5:31 PM, Allen Tom wrote:

> +100  - we'd be very happy to see an OpenID test suite!
>
> Allen
>
> Martin Atkins wrote:
>>
>> To complete this thought, I think a pre-requisite for work on 2.1  
>> is a comprehensive test suite for 2.0 and a harness to run the  
>> tests against popular implementations.
>>
>> This will allow changes made for 2.1 to be regression tested  
>> against existing implementations. For example, we could make an  
>> implementation that doesn't do the DH association step and see  
>> which implementations that breaks.
>>
>> _______________________________________________
>> general mailing list
>> general at openid.net
>> http://openid.net/mailman/listinfo/general
>
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general