Mark Rapp

Provided expert level QA support through manual functional and regression testing, a proven record of writing automation test scripts to drive regression coverage, and turning days of manual testing into minutes while bridging product requirements and developer delivery.

• I focus QA efforts on the highest‑value tests first, turning business risk into measurable automation deliverables.
• I write documentation and tests that make it easy for teammates to reproduce issues and keep quality consistent across releases.
• Served as QA Lead and subject matter expert for an Agile product team supporting Educator Licensure and Evaluation platforms.
• Designed and executed approximately 180 automated regression tests reducing manual pre‑release testing from 2 days to about 30 minutes.
• Stood up a Playwright automation framework proof of concept and added tests that validated core workflows and prevented regressions.
• Contributed automated tests and helper methods to an existing Selenium (C#) framework which validated core workflows and prevented regression issues.
• Wrote SQL queries to support manual testing efforts and for use in writing automated tests by inserting and manipulating test data.
• Shifted my testing balance from approximately 90% manual to 80% automated by prioritizing automation candidates and implementing focused test coverage.
• Wrote clear test cases in Azure DevOps, executed manual tests, and tracked defects in Jira using standardized reproduction steps and environment details.
• Investigated complex functional defects using exploratory testing, SQL, and log analysis; documented findings and recommended fixes to developers for rapid resolution.
• Authored Wiki documentation and detailed configuration posts to capture setup steps, gotchas, and data examples, improving team knowledge transfer and test reproducibility.

Helping deliver reliable software designed for Educator licensure and evaluation through practical testing, clear communication, and focused troubleshooting.

• Role summary: Analyze story cards and requirements to write prioritized test cases covering happy paths, edge cases, and negative scenarios. Execute manual tests and run automated suites to validate features and confirm release readiness.
• Testing focus: Lead functional testing for new features and core regression testing at sprint close; perform exploratory and ad-hoc testing to support developers and customer service. Wrote SQL Queries to find testing examples, insert test data, or to execute tests.
• Collaboration: Keep an ongoing dialog with developers and stakeholders to clarify requirements and resolve discrepancies; work with Customer Service to reproduce client reported bugs. Join release calls, perform production smoke tests after deployments.
• Quality: Catch defects early, maintain and the test library by archiving duplicates and updating out of date tests, and running accessibility scans to improve usability.

• Reduced missed requirements through QA / BA requirement reviews.
• Established test case repository for web functionality and future work.
• Assisted in bi-weekly stress testing via manual regression in production during the stress testing event.
• Backup tester for the QA Mobile Testing team.
• Performed Manual / Regression testing for the Regal Website
• Key Achievement: Assisted BA with Web requirements gathering by using combination of Mobile Emulator, Charles Proxy and Postman to document and test API endpoints used in the Mobile App.

• QA Lead for Policy Center. Engaging with QA's, Developers and Product Owners to facilitate coordination between Billing Center, Claims Center, and an automation engineer.
• Lead Test Automation effort to implement smoke tests.
• Track usage and availability of test environments, saving teams from overriding each other.
• Created and documented process to manually create and load test data (eMod factor) into Policy Center, saving 2 days of waiting.
• Key Achievement: Using only Blackbox testing techniques and estimated prediction models I was able to show that the DataRobot response would cause policies to be assigned to the wrong Insurance Company.

• Create & Peer Review Low-Level functional requirements.
• Creation / Execution of Manual and Keyword driven automated tests in a highly regulated environment.
• Create XML configuration files to interact with testing harness.
• Key Achievement: Wrote a Linux shell script which was included in the code base that validated proper installation of the Embedded System. This help to reduced device setup and verification from a full day to less than 30 minutes.

• Lead testing effort on customized GuideWire platform with 8 offshore QA team members across multiple projects which included Claims Center, Policy Center and Integrations.
• Review & validate automation and manual test scenarios produced and executed by QA department.
• Started and actively led defect triage meetings which eliminated duplicate defects and improved quality of defect reporting.
• Key Achievement: In preparation for hurricane season worked with the Automation Engineer to repurpose the framework to generate claim creation load which identified a bottleneck in the available server memory.

• Lead manual QA tester on a large SaaS Legal Case Management and Billing system spanning over 30 clients.
• Produced SQL queries to validate financial reporting.
• Create, execute, and maintain automation scripts using Selenium IDE for post production release testing over period of 3 years.
• Backup Release manager creating the weekly release candidate package and performed followup Git repository maintenance.
• Key Achievement: Reverse engineered Ruby / Selenium web driver automation framework and maintained the automation code base for 3 months.

• Testing and documentation of in-house XML loading tools based in a .Net environment.
• Key Achievement: Manual testing and SQL query execution efforts helped to achieve a 100% success rate of releasing XML/XSLT transformation content to production over a 2 month period.

• Designed, maintained & executed manual tests to meet gaming regulations.
• Validation of Client / Server communication using network monitoring tools.
• Key Achievement: Extreme attention to detail during a DOS to Windows conversion allowed for successful release of Gaming Machines to Mexico which met requirement of not giving away that an upgrade occurred.