*Hello,* * *
*Need Performance Tester with Property and Casualty experience is REQUIRED* *Long term duration* *Stevens Point, WI* At a minimum candidates should have - Expertise in what inputs are needed to create performance and load testing plans for the System Under Test. The candidate should be able to determine the type of tests needed, have the ability to execute them and be able to analyze the various performance counters to determine performance bottlenecks - Experience should cover load/performance/stress testing in web applications and databases. Knowledge of performance tools of operating systems and networking is important. - Experience with testing external facing web applications - Experience in writing/executing performance test plans - Solid experience with Load Runner and (5+ years preferred) - Good communication skills, motivated and driven to complete work assigned and works well independently - The following skills will be helpful for the position, but are not required: - Guidewire PolicyCenter experience - Java development experience - VB scripting and QTP experience - Decide whether to use internal or external resources to perform the tests, depending on inhouse expertise (or lack thereof) - Gather or elicit performance requirements (specifications) from users and/or business analysts - Develop a high-level plan (or project charter), including requirements, resources, timelines and milestones - Develop a detailed performance test plan (including detailed scenarios and test cases, workloads, environment info, etc) - Choose test tool(s) - Specify test data needed and charter effort (often overlooked, but often the death of a valid performance test) - Develop proof-of-concept scripts for each application/component under test, using chosen test tools and strategies - Develop detailed performance test project plan, including all dependencies and associated timelines - Install and configure injectors/controller - Configure the test environment (ideally identical hardware to the production platform), router configuration, quiet network (we don’t want results upset by other users), deployment of server instrumentation, database test sets developed, etc. - Execute tests – probably repeatedly (iteratively) in order to see whether any unaccounted for factor might affect the results - Analyze the results - either pass/fail, or investigation of critical path and recommendation of corrective action *Send resumes to [email protected]* -- R . PRADEEP KUMAR 919-290-7580
