QA cycle. Base pay + per bug bonuses

We have an enterprise website for online job applicants testing and recruitment process administration. We've recently done some wide changes in our code base, and would like to hire some help in verifying that nothing has been broken. In addition, we will be happy to form an ongoing relationship with a good tester and get further help from time to time. We'd like to hire someone for a set of 8 hours of QA. The QA will be done using IE6+ or FF3+, in front of our web servers. On top of the fixed, pre-agreed pay, we will pay some extra per each discovered bug (as detailed in the following fields). ## Deliverables On top of the base payment (the bid on this work), we will pay a bonus, based on the number of bugs found. We'd like to pay as follows: * We'll pay extra only for reproducible bugs (i.e. bugs that you can cause again and again through a defined scenario): * Crash error: cause error page to be displayed: $10 to $20 per page that generated the error (i.e. the same page with different query string parameters or scenario will not be counted twice). * Logic errors: * Something doesn't work: can't add an applicant, can't add a position, can't save changes, etc... - $10 to $20 per bug * Data corruption: a piece of data is entered but different data is displayed, or no data is displayed at all, etc... - $10 to $20 per bug. * GUI errors: * No extra pay for GUI bugs: we will be happy to hear about any GUI issue you find (misalignment, bad color, cut text, etc..) - but we won't pay bonuses for that. We expect to get "unique" bugs. For example, if you find that the character "^" inside a text field causes a crash, and then find that "^" inside another text field also causes a crash - it will be counted as ONE bug, not two. We will decide on the exact pay per bug (within the range specified above) - depending on the complexity of the scenario leading to that bug. If you find 10 bugs before the time is up - let us know and pause the haunt. We may want to review these bugs and consider whether to continue (we will of course pay for the full 8 hours anyway). We will retain the right to decide how to categorize a bug: whether it's a crash, a logic bug, a GUI bug or a duplicate of a previously found bug. We realize that this method of work and pay requires a certain level of trust. We are interested in forming a long-term relationship, and are willing to pay the aforementioned extras for a job that is done well. However, it is important for us that both sides will be happy at the end of the day. Please don't post a bid that you feel would not be enough for the 8 hours work if no bugs are found and no extra pay is given. Once we accept the bid - we will give a few short explanations about how the website is structured, but we expect you to be able to figure out most of it yourself. We don't plan to explain about every single field and button. The deliverables are to include: * An outline of the tests that have been performed (which routes were involved, which URLs, which operations, etc...). (This outline will be expected to match the records on our servers). * An organized and clear listing of bugs, with all the details required to reproduce them. * We may also request availability on MSN or Y!M to go over things, if the bugs listing will require clarifications.