BIND 10 #2078: lettuce test for bind10 -u
BIND 10 Development
do-not-reply at isc.org
Mon Jul 2 18:49:22 UTC 2012
#2078: lettuce test for bind10 -u
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: task | Status: new
Priority: | Milestone: New Tasks
medium | Resolution:
Component: Boss | Sensitive: 0
of BIND | Sub-Project: Core
Keywords: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:1 jelte]:
> may the test simply see whether it tries (and fails)?
I guess the intent was actually to see it works, considering the
background regression for this ticket...
> I'd be hesitant to require root privileges for these tests...
Me, too. This seems to be beyond the scope of system tests. On the
other hand, it would be nice if we can have some (semi?) automatic
test framework that tests the entire system in an environment closer
to actual deployments (using installed versions, with chuser, using
privilege port etc). If I hadn't tried to install and run the
"release candidate" on my server, it would have been very likely that
we included the #2067 regression in the release. I normally do this
check at least a few days before the release date for every release,
but it's not very reliable to only depend on such individual practice.
Such a test should probably be disabled by default, and would require
some special setup manually (becoming root, creating 'bind' user,
etc), and maybe manually invoked by hand a few days before the release
(or maybe run from root's cron periodically). (And it may not be
under the "lettuce" directory).
--
Ticket URL: <http://bind10.isc.org/ticket/2078#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list