Hi,
We have an open position at for “QA Tester / Validation Analyst*” at King of Prussia PA for 2 months. *Please review the job requirements and let me know if you're interested. Please provide the following Details along with your .doc RESUME. ** *Job Title: QA Tester / Validation Analyst* *Location: King of Prussia PA* *Duration: 2 months +* *Rate : DOE* * * *Job Description:* *MUST HAVE: GSK experience Preferred (iQMS is their internal validation protocol), Pharmaceutical validation experience (21 CFR part 11, etc), test plans, test cases, Mercury tools* Planning Phase • After requirements are complete, review and break down into functional areas. Determine what testing needs to be done. • Provide estimates (how much testing needed, type of testing needed, how much time to write/execute system testing and number testing resources needed). • Must be very familiar with requirements and how they map to the solution. • Create traceability between requirements and system test cases. • Write Test Plan. • Must be familiar with Validation Plan and iQMS GSOPs related to testing. • Determine whether performance testing will be needed. • Must be familiar with Mercury, Caliber and any other testing tools to be used. • Identify type of testing to be done during unit testing (example boundary). Ensure no duplication between unit and system testing. Design Phase • Drill deeper – map functional areas to logical requirements. • Work closely with developers to understand design of functional areas to test. Development Phase • Work with BA and developers to get answers to questions. • Review system test cases. • Help identify or setup test data. • Monitor defects during informal testing. Work with tech lead to determine whether these are really defects. • Perform informal testing. • Connect requirements to system test cases. Verify traceability for all requirements (as part of system test case review). • Communicate needed changes to tech lead (example usability issues). • Help determine how to verify expected results (are backend queries needed). Work with developers to get scripts written. Execution Phase • Monitor defects (same as informal testing). • Monitor testing results in Mercury. Monitor pass/fail results. Sometimes override test case pass/fail (if failed for one step but overall OK). • Make sure evidence was collected. • Make sure all tests were executed and at least one iteration passed. • Follow up with tech lead on failures (defects). • Make sure defect raised for each failure. • For defects, determine which tests need to be modified and/or re-executed. • Sometimes help execute test cases. • Help developers reproduce defects. • Make sure defects closed. • Generate test logs. • Make sure defects include comments on what was fixed and retested. • Write Test Report. • Modify surrounding regulated documents which are impacted by current project *Please respond with following Information: * First Name: Last Name: Availability-----: Visa Status (US Citizen, GC Holder, H1b or TN holder): Contact Number: E-mail Address: Hourly Rate: Re-location: Current Location (Place & State): Last 5 SSN : *Thanks & Regards, * * * *Venu* CompuSoft Integrated Solutions, Inc. **Inc. 5000 Fastest-Growing Private Company Award - 2008* Ph: 248-522-6862 Fax: 248-538-8435 E-mail: ve...@compusoft-is.com <blocked::mailto:ve...@compusoft-is.com>; madhav_compus...@yahoo.com <blocked::mailto:madhav_compus...@yahoo.com>; URL: www.compusoft-is.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Open Source Erp & Crm" group. To post to this group, send email to open-source-erp-crm@googlegroups.com To unsubscribe from this group, send email to open-source-erp-crm+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-source-erp-crm -~----------~----~----~----~------~----~------~--~---
