Patrick Wahl Email & Phone Number

Kalispell, Mt

Kalispell, Montana

QA Analyst responsible for creating and executing test cases based on requirements. Testing focused on homeowners insurance. On the large project team I was co-lead on project cycles. Co-lead meant we would alternate on who would lead each project. I was responsible in handling metrics which would account for estimates, time spent and number of defects. This document would help us analyse at the end of a sprint where we went over our estimates or if we had too many defects compared to the prior project. I would also do intensive rater testing manually. For some of the manual UI tests I would update automation inputs that were set up by our automated testing team, analyze results and submit defects if needed. I frequently leveraged my SQL skills to join multiple tables would allow me to pull specific test data needed or validate test cases. I would also execute stored procedures to move data into different states needed for validation. One example of this would be using the stored procedure to change the state of a pending cancel policy to cancelled. I also used Jmeter which is a performance testing tool to generate test data. Jmeter would be configured to pull data from a CSV file, input the data into a quote and process a call for credit score. I found many correlations in terminology with flood insurance and homeowners insurance working here. I assisted the QA manager in interviewing prospective QA resources. The QA manager valued my interview skills and input on new candidates. I also assisted the team in assessing new QA tools for our team.

Kalispell Montana

As a QA Analyst for National Flood Services I was responsible for validating stories assigned to me during 2 to 3 week sprints. During planning meetings I would join the other scrum team members in estimating the weight of each story and how many hours QA would have to work it during the sprint. Every day we have a scrum meeting where we describe what tasks we have worked on and what is left to do. After this we create test plans, review them with QA or developers and then with the whole team. Using PL SQL developer tool we deploy our release to the QA environment. After validation is complete we demo the testing results to the team so that they have an understanding of the work done during the current sprint. Next, released stories are deployed to production environment and validated using deployment test plans. Testing requires SQL knowledge for running advanced database queries, validation of stories and as a way to acquire or create test data. I also created and executed a set of security tests using Jmeter to assist them with complying with a security audit.

Spokane, Washington Area

As a QA analyst working for Ambassadors group I was responsible for managing quality assurance for 3 scrum teams. During the sprint planning meeting I would get a sense of the testing effort required and make sure that requirements included acceptance criteria. I would submit project status for all 3 teams during our morning scrum meetings. Test cases would be assigned to various business resources and results tracked. This was necessary due to having a limited number of QA resources. I would use SQL server to validate data via databases. I would have to make direct changes to the database and run SSIS packages to move data to different systems. I would use SOAPUI to run quick validations, create test data or run regression suites. To succeed I would have to be comfortable collaborating with the business, operations and developers. I was also responsible for maintaining a manual regression set that would be ran every week. Using Visual Studio I would run an automated regression suite every week and report results. SOAPUI was used to run a regression set that would target specific endpoints.

Pendleton, Oregon

Test lead responsible for project release validation through complete software development cycle. During grooming sessions we review the stories with the requirements writer, developers and operations team. Once stories are received in RTC I create tests and either assign them to myself or the other member of the browser experience team. With creating the testing task I also estimate the time it will take, assign priority and include the actual time taken to run the tests. During my IST test run I am have to enter defects and assign them. Occasionally it is necessary to participate in working sessions with development and operations to find solutions. Daily reports are sent to the project manager outlining defects and current issues blocking testing. When all defects are resolved and all tests are passed I can validate that the IST has passed in stage environment. Results from IST testing are demoed to the stakeholders during a meeting at the end of the sprint. When project has successfully deployed to stage I am responsible for running the final production test. My testing scope is purely black-box and runs from IST to final production pass. I am not responsible for unit (code) or assembly test passes. Those are handled by the development team. Testing scope focuses on security, encryption and authentication.

Liberal Arts And Sciences, General Studies And Humanities

Liberal Arts And Sciences, General Studies And Humanities

High School Diploma