Your SlideShare is downloading. ×
0
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
2008 11 08 Bughuntday
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

2008 11 08 Bughuntday

4,191

Published on

Slides of the Zend Framework Bughuntday on saturday November 8th.

Slides of the Zend Framework Bughuntday on saturday November 8th.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,191
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
10
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  1. Bug Hunt Day Zend Framework
  2. This help is sorely needed, and we appreciate your efforts! First, Thank you! “
  3. Introduction <ul><li>Jurriën Stutterheim </li></ul><ul><li>Also known as norm2782 </li></ul><ul><li>Zend Framework Core Contributor </li></ul><ul><ul><li>Zend_Paginator (co-author Matthew Ratzloff) </li></ul></ul><ul><ul><li>Zend_Controller_Action_Helper_MultiPageForm </li></ul></ul><ul><ul><li>Zend_Feed_Reader (main author Pádraic Brady) </li></ul></ul>| Nov 4, 2008 Introduction |
  4. The process <ul><li>Query the issue tracker for bugs </li></ul><ul><li>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 </li></ul><ul><li>Write a test to reproduce the bug </li></ul><ul><li>Run the test to ensure that it fails </li></ul><ul><li>Write code to fix the failing test </li></ul><ul><li>Run the test to verify the fix </li></ul><ul><li>Commit the test and code to the bughuntday branch </li></ul><ul><li>Tell the issue tracker you've finished work </li></ul><ul><li>Resolve the issue </li></ul>| Nov 4, 2008 The process |
  5. Query the issue tracker <ul><li>http://framework.zend.com/issues </li></ul><ul><li>Click “Find Issues” </li></ul><ul><li>Select: </li></ul><ul><ul><li>Project: Zend Framework </li></ul></ul><ul><ul><li>Issue Type: Bug </li></ul></ul><ul><ul><li>Resolutions: Unresolved </li></ul></ul><ul><ul><li>Optionally, choose specific component(s) </li></ul></ul>| Nov 4, 2008 Query the issue tracker |
  6. Query the issue tracker | Nov 4, 2008 Query the issue tracker |
  7. Identify a bug to fix; mark it as in progress | Nov 4, 2008 Identify a bug to fix; mark it as in progress |
  8. In progress... | Nov 4, 2008 In progress... |
  9. Write a test case to reproduce the bug <ul><li>When choosing bugs, prioritize bugs that have reproduce code over those that do not </li></ul><ul><li>Test names should reflect the functionality being tested </li></ul><ul><li>Test method should have an @group annotation with the issue identifier </li></ul>| Nov 4, 2008 Write a test case to reproduce the bug |
  10. Write a test case to reproduce the bug | Nov 4, 2008 Write a test case to reproduce the bug |
  11. Run the test to verify it fails | Nov 4, 2008 Run the test to verify it fails |
  12. Run the tests to verify your fix <ul><li>Fixed! </li></ul>| Nov 4, 2008 Run the tests to verify your fix |
  13. Commit your changes... <ul><li>“ svn ci”: </li></ul>| Nov 4, 2008 Commit your changes... | <ul><li>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: </li></ul>
  14. Note the revision number <ul><li>In this case, r12281 </li></ul>| Nov 4, 2008 Note the revision number |
  15. Tell the tracker you're done | Nov 4, 2008 Tell the tracker you're done |
  16. Resolve the issue in the tracker <ul><li>Indicate the SVN revision </li></ul><ul><li>Indicate what branch the resolution exists in (bughuntday) </li></ul>| Nov 4, 2008 Resolve the issue in the tracker |
  17. Resolve the issue in the tracker | Nov 4, 2008 Resolve the issue in the tracker |
  18. Contributer License Agreements <ul><li>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. </li></ul><ul><li>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. </li></ul><ul><li>Your issue tracker username will be used to track commits. </li></ul><ul><li>All committers should note the username of the originating developer as part of the log message; otherwise, we will assume it's your own. </li></ul>| Nov 4, 2008 Contributer License Agreements |
  19. On IRC <ul><li>Join the fun on IRC </li></ul><ul><li>#zftalk.dev on irc.freenode.net </li></ul>| Nov 4, 2008 Contributer License Agreements |
  20. Thank you for supporting Zend Framework today! And again, Thank you! “

×