BIND 10 #1007: create a higher granularity of exceptions for xfrin/xfrout

[BIND 10 Development]

#1007: create a higher granularity of exceptions for xfrin/xfrout
-------------------------------------+-------------------------------------
            Reporter:  zzchen_pku    |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 See Jinmei's comments below:
 {{{
 xfrin and xfrout use the same single exception in so many places,
 obscuring the accuracy of test results.
 When we do self.assertRaises(XfrinException?, xxx), we cannot really be
 sure if the exception is really
 triggered at where it should be triggered.
 We could check the exception error message , but since the error message
 tends to be modified it will be
 unstable. I guess we'll need a higher granularity of exceptions (or sub
 types of them) for these apps.
 }}}

-- 
Ticket URL: <http://bind10.isc.org/ticket/1007>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development