[Opendnssec-develop] RE: Regression testing update

Sara Dickinson sara at sinodun.com
Thu Dec 6 14:29:29 UTC 2012


On 6 Dec 2012, at 14:16, Siôn Lloyd wrote:

> On 06/12/12 14:10, Sara Dickinson wrote:
>> Hi, 
>> 
>> Also on this topic I have another suggestion.... 
>> 
>> When we make svn commits that are purely regression test related, how about we use the following format for the update:
>> 
>> TEST: Add new method called blah to test framework.
>> TEST (enforcer-keys-backup-1): Add new test script to cover.....
>> 
>> In other words in the same way we use OPENDNSSEC/SUPPORT as identifiers for bug fixes we use TEST to show the update is purely test related (a specific test name is a nice to have). It will make life (well, my life for sure :-) ) much easier when looking through lots of subversion updates to be able to ignore things that haven't affected the functionality of the product. 
>> 
>> WDYT?
>> 
>> 
> 
> Works for me. We'd have to commit tests and functionality in separate
> revisions, but I don't see that being an issue.
> 

Good point - but that does seem to be how most people work at the moment.... And could always do:

SUPPORT-XX & TEST: Fix bug and update regression test

> Sion
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop




More information about the Opendnssec-develop mailing list