[Opendnssec-develop] testing dns adapters document

Sara Dickinson sara at sinodun.com
Wed Oct 31 12:42:57 UTC 2012

On 31 Oct 2012, at 10:37, Matthijs Mekking wrote:

> Hi,
> On 10/31/2012 11:29 AM, Sara Dickinson wrote:
>> Hi Matthijs, 
>>> From looking at this it seems to me the following are rough areas to concentrate on:
>> 1) Would it be best (if possible) to get someone else to do some manual testing of TCP & ACL to try to catch any major issues if this is too time consuming to do in jenkins right now?
> That would certainly be useful.

I can take a pass at the ACL stuff later this week - any volunteers for the TCP side of things?

>> 2) In terms of jenkins tests then as you said, it seems focussing on IXFR functionality and scalability seems the obvious thing to prioritise. 
> IXFR functionality is something that can be put in jenkins. Scalability
> tests seems to me has to be done on a different platform.
>> 3) I wonder if we should also consider setting up a jenkins test with the adapters using BIND and possibly validns on just one platform (since we don't know when we will have the benchmarking hardware). This could use a separate test directory and jenkins test and run once a day. It would give us a baseline and hopefully catch some issues. Given we no longer have the auditor we need to start thinking about other validation mechanisms anyway. I don't think the fact we can't support it easily on all platforms is an argument for not doing it at all?
> Either on one jenkins platform or outside jenkins, an interoperability
> test that can be replayed would be very nice to have. With that in mind,
> putting it in the daily test dir in jenkins would make sense to me. Lets
> see how far we can get with the scripts from Nominet.

Jerry - could you help out with setting up BIND and validns (or similar) for this work?



More information about the Opendnssec-develop mailing list