Merge lp:~jtv/launchpad/son-of-bug-487447 into lp:launchpad
Proposed by
Jeroen T. Vermeulen
Status: | Merged |
---|---|
Approved by: | Henning Eggers |
Approved revision: | not available |
Merged at revision: | not available |
Proposed branch: | lp:~jtv/launchpad/son-of-bug-487447 |
Merge into: | lp:launchpad |
Diff against target: |
224 lines (+71/-4) 2 files modified
database/schema/security.cfg (+1/-0) lib/lp/translations/tests/test_translationbranchapprover.py (+70/-4) |
To merge this branch: | bzr merge lp:~jtv/launchpad/son-of-bug-487447 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Henning Eggers (community) | code | Approve | |
Review via email: mp+16480@code.launchpad.net |
Commit message
Fixed regressed permissions problem for branch approver.
To post a comment you must log in.
= Bug 487447 (regression) =
This bug, a missing database permission, just regressed. It's a bit hard to maintain complete test coverage because the same permissions are to an extent shared by two scripts, each with its own database user. The original fix unified those permissions; before that, they were duplicated. In this case, one of the two scripts had the needed privilege but the other one didn't.
Unfortunately I found no test that covered this from the right angle (database permissions for the branch approver), so I extended the existing unit test to switch database identities; and then I added a test for the part that breaks. It reproduces the bug as expected.
Some private methods in the test violate our naming standards (which mandate dromedaryCase instead of lower_case_ with_underscore s) but for the sake of brevity I decided not to touch them. If you so desire, dear reviewer, this can still be changed.
To Q/A, create a product with a template in one series; the template should have its base filename as its name and domain. Make some translations to ensure that it has POFiles. Then set up bzr imports for another release series, and commit a template with the same filename as the first one. Within an hour after pushing that branch, the template you pushed there should show up as Approved in the project's import queue.
Test: chapprover
{{{
./bin/test -vv -t translationbran
}}}
No lint.
Jeroen