Closed Bug 1011263 Opened 11 years ago Closed 11 years ago

The qa test suite should have a master branch that bugzilla master run against

Categories

(Bugzilla :: QA Test Scripts, enhancement)

Product:
Bugzilla
Component:
QA Test Scripts
Version:
4.5.6
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: dkl, Assigned: dkl)

Details

When we fork a new branch for release we can then fork the master qa branch as well to match like we do now. We should have a master branch that is there for commits to bugzilla master to run against. dkl
Not a blocker. We survived very well till now without a master branch for QA.
Severity: blocker → enhancement
OS: Linux → All
master branch has been created now (copied from 4.4) and will need to spend some time going through the failing tests. dkl
QA test fixes: To ssh://gitolite3@git.mozilla.org/bugzilla/qa.git e24c6e1..b63c820 master -> master trunk travis.yml changes: To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git 5656590..33df23c master -> master dkl
Assignee: testing → dkl
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Version: 4.5.4 → 4.5.6
I reverted changes you made in test_custom_fields.t. They were wrong and caused test failures. To ssh://gitolite3@git.mozilla.org/bugzilla/qa.git e52547d..3733e37 master -> master To ssh://gitolite3@git.mozilla.org/bugzilla/qa.git 4ae9eca..c70cd5d 5.0 -> 5.0
You need to log in before you can comment on or make changes to this bug.