Status

()

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: glob, Assigned: dkl)

Tracking

Production

Details

(Reporter)

Description

3 years ago
not ok 786 - XML-RPC: adding valid group that is not in this product fails
not ok 787 - XML-RPC: Got correct fault for Bug.update
not ok 788 - XML-RPC: Fault code is set properly
(Assignee)

Updated

3 years ago
Assignee: nobody → dkl
Status: NEW → ASSIGNED
(Assignee)

Comment 1

3 years ago
Note to self:

We allow setting a group as a security group in the editproduct.cgi UI even if it is not visible on the product. The test suite expects an error to occur when trying to set a group that is not visible. But the following code in BMO/Extension.pm allows it:

# you can always file bugs into a product's default security group, as well as
# into any of the groups in @always_fileable_groups
sub _group_always_settable {
    my ($self, $group) = @_;
    return
        $group->name eq $self->default_security_group
        || ((grep { $_ eq $group->name } @always_fileable_groups) ? 1 : 0);
}

Need to figure out how QA-Selenium-TEST group is getting set to the security group instead of core-security.
(Reporter)

Comment 2

3 years ago
can we disable this test until this is fixed?
(Assignee)

Comment 3

3 years ago
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
   22d71ed..dc87344  master -> master
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.