First Last Prev Next    This bug is not in your last search results.
Bug 593648 - sasl testing cannot be fully automated
sasl testing cannot be fully automated
Status: CLOSED UPSTREAM
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
Development
All Linux
high Severity high
: ---
: ---
Assigned To: mick
MRG Quality Engineering
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-05-19 07:55 EDT by mick
Modified: 2010-09-09 13:12 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-09 13:12:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description mick 2010-05-19 07:55:38 EDT 
Currently, the Cyrus-SASL library code that we use reads its configuration information only from the standard installed locations such as /etc/sasl2 .
Because of this, our testing cannot run without messing with the standard location, which is probably not what our users or developers are expecting.  Not to mention that doing so probably requires root access...

This means that, currently, we do not automate SASL-related testing.  It can only be done on systems that we have manually prepared in advance.

Fix this so that SASL-related tests can run like all of our other "make check" tests.
Comment 1 mick 2010-05-24 14:40:09 EDT 
fixed by svn rev 947748.

new test run_sasl_authentication_test created in "make check"
and
run_sasl_authentication_soak in "make check-long"
Comment 2 Gordon Sim 2010-09-09 13:12:12 EDT 
This change was made upstream; not directly relevant to customers or releases so closing.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.