Opened 7 years ago

Closed 6 years ago

#2294 closed task (wontfix)

Lettuce test for long-running xfr-out

Reported by: vorner Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: xfrout Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 5 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


It turned out in #2222 that it's hard to test the fact that statistics number
of currently running transfers is incremented when the transfer starts and then
decremented after the transfer.

We need a support to have a longer-running transfer. The proposal is to have
larger zone and a client that starts the transfer, but does not eat the data
off the TCP connection, so the buffers fill. We then can wait as long we need
to check the statistics counters.

This capability could be used for more things than just that, for example, we
could try running more transfers in parallel.


Change History (5)

comment:1 Changed 7 years ago by muks

Can mock objects not help here?

comment:2 Changed 7 years ago by vorner

Mock objects are good for unit tests. But we want to test the system as a
whole. Interaction with b10-stats is probably one of the things to test as a

comment:3 Changed 7 years ago by shane

  • Milestone New Tasks deleted

comment:4 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:5 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check

Closing ticket.

Note: See TracTickets for help on using tickets.