Upgrade to Pro — share decks privately, control downloads, hide ads and more …

QA and bibisecting in a huge software project

QA and bibisecting in a huge software project

Avatar for Bjoern Michaelsen

Bjoern Michaelsen

January 01, 1970
Tweet

More Decks by Bjoern Michaelsen

Other Decks in Programming

Transcript

  1. 2 Random comment on the Interwebz “Have you ever tried

    to contribute to OpenOffice? The project is infamous for basically ignoring the contributions of the non-blessed.” – Anonymous guy on the net
  2. 3 Why starting at QA If you are shy about

    contributing, QA is a great way to get started: You interact with developers You learn how the developers work You will be more confident about contributing code on your own
  3. 4 Verify a fix! Go to bugzilla Search for bugs

    in resolution “fixed” Get a daily build and see if the bug is indeed fixed How does this help: Commits that fix a bug are usually linked in bugzilla – so you can learn about how it was fixed Sometimes, fixing a bug creates a new one ;)
  4. 5 Confirm a reported bug! Go to bugzilla Search for

    bugs in status “unconfirmed” How does this help: A confirmed bug can be assumed to be well-described A bug report that cannot be confirmed will lead to additional useful information collected