#286 Verbosity of collection unit tests must be lowered
Closed: Fixed None Opened 14 years ago by sgallagh.

The verbosity level of the collection tests is far too high to be useful. By default, it should print only errors.

Bonus points for allowing full verbosity by an environment variable.


The unit tests are completely worthless right now because if they fail, locating the offending message is nearly impossible. It's marked critical only because that just happened to be the priority one above "major" (which is the default).

I do not think it is a priority at all because if it fail the error will be right at the end of the output so there is no problem in finding it. The things that flew by are not important if you just care about the errors.

I will fix it later and make it more readble at the same time to do other re-factoring for collection.

milestone: SSSD 1.0 => SSSD Deferred
priority: critical => minor

Patches to do this are already either committed or on the list to review.

proposed: => 1.1

Fields changed

milestone: SSSD Deferred => SSSD 1.1

Changeset 3c401be

fixedin: => 1.1.0
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to dpal
- Issue set to the milestone: SSSD 1.1

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1328

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata