1 / 9

Test Approach OpenDNSSEC 1.2

Test Approach OpenDNSSEC 1.2. December 2010. 1. Contents - Goal - Scope - Phasing - Test Scripts - Planning - Preconditions. 2. Goal Testing OpenDNSSEC 1.2 by varying policies and zone contents to measure the level of quality of ODS 1.2 and prove it's quality to the community. 3.

arich
Download Presentation

Test Approach OpenDNSSEC 1.2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test Approach OpenDNSSEC 1.2 December 2010 1

  2. Contents - Goal - Scope - Phasing - Test Scripts - Planning - Preconditions 2

  3. GoalTesting OpenDNSSEC 1.2 by varying policies and zone contents to measure the level of quality of ODS 1.2 and prove it's quality to the community. 3

  4. Scope- Bugfixes- Performance with many small zones (50.000+)- Shared keys- All different RR types- KASP functionality- Varying Zone content- New dependencies (ldns1.6.7, SoftHSM1.2, dnsruby1.51)- Zonefetcher - Extensive communication on test status 4

  5. Phasing1. Set up test organization 2. Prepare test scripts3. Execute test scripts – System (Integration) Test – (ST/SIT) 4. Report System Test5. Execute test scripts – Acceptance Test (AT) 6. Report Acceptance Test

  6. Test Scripts 6

  7. Planning 7

  8. Preconditions– Availability of System administrators first 2 weeks an average of 1 hour per day. Following weeks 3 hours per week; – Availability of the puppet system to create “one-button” test environment in form of Virtual Machines with designated software pre-installed (ODS, SoftHSM); – Parttime availability of Freddy Keurntjes for test engine support during test execution and rework (4 hours a day); – Weekly conference call with ODS team for status update; – Extensive communication on bugfixes and new releases; – Availability of ODS project members for support with an average of 4 hours a week 8

  9. Feedback 9

More Related