Download Safari Books Online apps: Apple iOS | Android

Entire Site

Safari Books Online

    Free Trial

    Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


    Head First Software Development
    Dedication
    A Note Regarding Supplemental Files
    Advance Praise for Head First Software Development
    Praise for Head First Object-Oriented Analysis and Design
    Praise for Head First Design Patterns
     
    How to use this Book: Intro
    1. Great Software Development: Pleasing your customer
    2. Gathering Requirements: Knowing what the customer wants
    3. Project Planning: Planning for success
    4. User Stories and Tasks: Getting to the real work
    5. Good-Enough Design: Getting it done with great design
    6. Version Control: Defensive development
    7. Building your Code: Insert tab a into slot b...
    8. Testing and Continuous Integration: Things fall apart
    9. Test-Driven Development: Holding your code accountable
    10. Ending an Iteration: It’s all coming together...
    Your iteration is just about complete...
    ... but there’s lots left you could do
    Standup Meeting
    System testing MUST be done...
    ... but WHO does system testing?
    System testing depends on a complete system to test
    Good system testing requires TWO iteration cycles
    More iterations means more problems
    The life (and death) of a bug
    So you found a bug....
    Anatomy of a bug report
    But there’s still plenty left you COULD do...
    Time for the iteration review
    Some iteration review questions
    A GENERAL priority list for getting EXTRA things done...
    Tools for your Software Development Toolbox
    11. The Next Iteration: If it ain’t broke... you still better fix it
    12. Bugs: Squashing bugs like a pro
    13. The Real World: Having a rocess in life
    A. Leftovers: The top 5 topics (we didn’t cover)
    B. Techniques and Principles: Tools for the experienced software developer
    Index
    About the Authors
    Copyright
    • Create BookmarkCreate Bookmark
    • Create Note or TagCreate Note or Tag
    • PrintPrint
    Share this Page URL
    Help

    Anatomy of a bug report

    Different bug tracking systems give you different templates for submitting a bug, but the basic elements are the same. As a general rule of thumb, the more information you can provide in a bug report, the better. Even if you work on a bug and don’t fix it, you should record what you’ve done, and any ideas about what else might need to be done. You—or another developer—might save hours by referring to that information when you come back to that bug later.

    A good bug report should have:

    Summary: Describe your bug in a sentence or so. This should be a detailed action phrase like “Clicking on received message throws ArrayOutOfBoundsException,” not something like “Exception thrown.” You should be able to read the summary and have a clear understanding of what the problem is.

      

    You are currently reading a PREVIEW of this book.

                                                                                            

    Get instant access to over
    $1 million worth of books and videos.

      

    Start a Free Trial