629164 - Test is_mandatory in the return value for Bug.fields

Status: RESOLVED FIXED

(Bugzilla :: QA Test Scripts, enhancement)

Description

[Max Kanat-Alexander]

Bug.fields now returns is_mandatory, which is a new field, for Bugzilla 4.0. We need to test that its value is correct.

Comment 1

[David Lawrence [:dkl]]

Attachment: Patch to check if certain fields are set mandatory (v1)

Patch to webservice_bug_fields.t to check if certain fields are set is_mandatory in the returned data.

Dave

Comment 2

[Max Kanat-Alexander]

Ah, also check that some other fields are not mandatory.

Comment 3

[Colin Ogilvie [:cso]]

Comment on attachment 510453 [details] [diff] [review]
Patch to check if certain fields are set mandatory (v1)

You seem to have a stray ` at the end of the "plan tests" line...

Comment 4

[David Lawrence [:dkl]]

Attachment: Patch to check if certain fields are set mandatory (v2)

Something like this is better?

Dave

Comment 5

[Max Kanat-Alexander]

Comment on attachment 510730 [details] [diff] [review]
Patch to check if certain fields are set mandatory (v2)

Ah, this is just a patch that entirely removes webservice_bug_fields.t. Also, this included your selenium_test.conf--you might want to do a "bzr commit --local config/selenium_test.conf" before creating your patch.

Comment 6

[David Lawrence [:dkl]]

Attachment: Patch to check if certain fields are set mandatory (v3)

Sorry bout the previous patch. Here is the correct one for review.

Dave

Comment 7

[Max Kanat-Alexander]

Comment on attachment 511068 [details] [diff] [review]
Patch to check if certain fields are set mandatory (v3)

Looks good to me. :-)

Comment 8

[David Lawrence [:dkl]]

qa/4.0:
Committing to: bzr+ssh://[e-mail]/bugzilla/qa/4.0/
modified t/webservice_bug_fields.t
Committed revision 178.

Comment 9

[Frédéric Buclin]

I finally decided to set the approval flag in the QA component, so that we can more easily track which scripts landed on which branches.