#667: Error rendering forbidden pages
------------------------+---------------------------------
Reporter: olemis | Owner: olemis
Type: defect | Status: closed
Priority: blocker | Milestone: Release 8
Component: ui design | Version: 0.7.0
Resolution: fixed | Keywords: permissions, chrome
------------------------+---------------------------------
Changes (by rjollos):
* status: assigned => closed
* resolution: => fixed
Comment:
Part of the test case is fine because a product is created that isn't used
in any other tests and therefore we don't have to worry about coupling.
However we shouldn't change the test environment just because you can find
some cases where this is done in the Trac codebase. Changes to
//trac.ini// and the permissions system should generally be restored at
the end of the test case.
The test case doesn't fail when run against the codebase prior to r1528323
because there are still navigation items rendered due to anonymous having
permissions at global scope. The test case was fixed and confirmed to
failed against r1528322 before it was committed.
---
(In [1542473])
0.8dev: Added a functional test for rendering forbidden pages. Refs #667.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/667#comment:17>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
