[development] DrupalWebTestCase and changing permissions of authenticate user role
Maarten van Grootel
mvgrootel at gmail.com
Mon Aug 25 21:08:51 UTC 2008
You're right, I can just work around it. I have to admit that I didn't think
of 'visiting' admin/user/permissions, but that's what this mailinglist is
Thanks for your input,
On Mon, Aug 25, 2008 at 4:45 PM, Nathaniel Catchpole <catch56 at googlemail.com
> Hmm. I think you're probably right.
> There's nothing stopping you from changing the permissions as part of your
> test though, you can visit admin/user/permissions and save the form with
> different values, or just delete the row from the permissions table directly
> with db_query().
> That said, I'm not sure how much this is by design, or an omission in
> On Mon, Aug 25, 2008 at 3:20 PM, Maarten van Grootel wrote:
>> Hi Nat,
>> That's not what it says, or at least not what's happening. It says that if
>> null, it receives the default permissions stated in _drupalCreateRole()
>> (which is array('access comments', 'access content', 'post comments', 'post
>> comments without approval') according to
>> But, this does not influence the permissions every user receives by the hard
>> coded Authenticated User role. Not directly, but by association/inheritance.
>> This behavior is expected, because it's the Drupal way of permission
>> inheritance. But to test the behavior I still need to find a way to alter
>> the permissions not my newly created user+role, but of the global
>> Authenticated User Role. You can try it by removing 'post comments' from row
>> 27 of comment.test. You'd expect al sorts of failures, because you just made
>> web_user not able to create comments, but everything passes effortlessly.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development