Ongoing QA for prerelease Windows application

I need help in doing quality assurance and testing for a MFC-based Windows application. I'm eager to establish an ongoing relationship with someone skilled in QA. The first part of this project is to create a test plan. Unfortunately, there is no formal requirements document for the product, so development of test cases will come from Contractor's observations and expectations of application behavior as well as collaboration and feedback from me. The test plan will be extended over time as the product gains new features. The second and ongoing part of the project is to execute the test plan against successive beta releases of the product, provide a report of issues found, and enter bugs into a Web-based bug tracking system (Mantis). Current plan is to have a new beta release every 45-60 days. Contractor should be able to complete quick "smoke tests" within 1-2 business days of receiving a release candidate. Contractor would be encouraged to use test automation tools if appropriate, and I am willing to discuss buying licenses for tools for Contractor's use (although budget is limited). The product is intended to be compatible with Windows 98 SE and later, so Contractor will need access to real or virtual machines running Win98SE, WinME, Win2000, WinXP (original, SP1, SP2). Test coverage on a variety of machines and configurations is highly desirable. I'll provide more details about the product to interested bidders via private posts here. ## Deliverables 1) Complete test plan, provided in MS Office-editable format. Contractor may generate this document by exporting from a QA tool as necessary. 2) When test plan is accepted, report of execution of test plan against software provided to contractor. 3) Entry of defects found into online bug tracking system. 4) Source or other editable form for any macros, tools, scripts, etc. that Contractor creates for purposes of testing. ## Platform Windows 98 SE and later.