Copyright © 2007, Zend Technologies Inc.

Bug Hunt DayZend Framework

This help is sorely needed, and we appreciate your efforts!“

First, Thank you!

| Nov 4, 2008Introduction | 3

Introduction

• Jurriën Stutterheim

• Also known as norm2782

• Zend Framework Core Contributor• Zend_Paginator (co-author Matthew Ratzloff)

• Zend_Controller_Action_Helper_MultiPageForm

• Zend_Feed_Reader (main author Pádraic Brady)

| Nov 4, 2008The process | 4

The process

• Query the issue tracker for bugs

• Identify a bug you want to work on, and indicate you're working on it by leaving a comment, assigning it to yourself and marking it In Progress

• Write a test to reproduce the bug

• Run the test to ensure that it fails

• Write code to fix the failing test

• Run the test to verify the fix

• Commit the test and code to the bughuntday branch

• Tell the issue tracker you've finished work

• Resolve the issue

| Nov 4, 2008Query the issue tracker | 5

Query the issue tracker

• http://framework.zend.com/issues

• Click “Find Issues”

• Select: Project: Zend Framework Issue Type: Bug Resolutions: Unresolved Optionally, choose specific component(s)

| Nov 4, 2008Query the issue tracker | 6

Query the issue tracker

| Nov 4, 2008Identify a bug to fix; mark it as in progress | 7

Identify a bug to fix; mark it as in progress

| Nov 4, 2008In progress... | 8

In progress...

| Nov 4, 2008Write a test case to reproduce the bug | 9

Write a test case to reproduce the bug

• When choosing bugs, prioritize bugs that have reproduce code over those that do not

• Test names should reflect the functionality being tested

• Test method should have an @group annotation with the issue identifier

| Nov 4, 2008Write a test case to reproduce the bug | 10

Write a test case to reproduce the bug

| Nov 4, 2008Run the test to verify it fails | 11

Run the test to verify it fails

| Nov 4, 2008Run the tests to verify your fix | 12

Run the tests to verify your fix

• Fixed!

| Nov 4, 2008Commit your changes... | 13

Commit your changes...

• “svn ci”:

• Good commit messages include the issue identifier, the name of the person fixing (since not all of you have commit rights), and a brief message describing the fix:

| Nov 4, 2008Note the revision number | 14

Note the revision number

• In this case, r12281

| Nov 4, 2008Tell the tracker you're done | 15

Tell the tracker you're done

| Nov 4, 2008Resolve the issue in the tracker | 16

Resolve the issue in the tracker

• Indicate the SVN revision

• Indicate what branch the resolution exists in (bughuntday)

| Nov 4, 2008Resolve the issue in the tracker | 17

Resolve the issue in the tracker

| Nov 4, 2008Contributer License Agreements | 18

Contributer License Agreements

• You must have signed previously or sign today a Contributor License Agreement. If you are not willing to do so, please do not contribute changes.

• If you have not signed a CLA yet, do so today, and get it faxed/emailed to cla@zend.com no later than Monday morning.

• Your issue tracker username will be used to track commits.

• All committers should note the username of the originating developer as part of the log message; otherwise, we will assume it's your own.

| Nov 4, 2008Contributer License Agreements | 19

On IRC

• Join the fun on IRC

• #zftalk.dev on irc.freenode.net

Thank you for supporting Zend Framework today!“

And again, Thank you!