OBJECTIVE:

Senior QA Analyst \ Lead position to focus my many years of testing experience to help management move forward in implementing test strategies, enhance software quality, develop automation scripts for regression testing and creating unique software tools to make QA processes more efficient along with meeting manual test goals.

SUMMARY:

• 16 Years of QA automation experience with Confidential, Winrunner, Silktest, SilkPerformer, Loadrunner, AutoIT freeware, GUI and command line automation using various Perl and Java harnesses. 5 years total experience working with SAP systems.
• Years of experience developing many test plans, test scripts and entering defects using ALM 11.
• Worked in QA departments in IT software companies and pharmaceutical companies developing processes for QA and using my software expertise to establish quality standards.
• Years of experience working with Solaris Unix, Linux, IOS, and Windows operating systems.
• In order to test for Confidential, it required testing on all four OS platforms.
• Database experience with SQL Server, Oracle, MySQL and MS Access.
• Participated in change review meetings with development on how the quality would be affected and if the proposed changes should be permitted to proceed for the next build of software to be released to customers.
• Used Excel and ALM 11 to generate metrics for obtaining software quality and evaluating results.
• Confidential Clearance achieved at Confidential, Secret Level. Performed several months of performance testing with Jmeter at Confidential .
• Used SoapUI to send orders to the SAP system for processing with XML as the order medium.
• Familiar with Java and Perl, Mercurial, TortoiseHG, and Selenium/Protractor/AngularJS Worked in an Agile development environment with Rally and bi - monthly sprints.
• Used Jenkins with CI to control Automation scripts with new builds, and JIRA for Agile/Scrum process.
• Used Selenium for running and creating automation of various web browsers.
• Created Confidential automation for a salesforce.com website frontend

WORK EXPERIENCE:

Confidential, Boulder, CO

Lead QA Analyst

Responsibilities:

• Created test processes and procedures for a new QA team that was formed
• Scrum/Agile QA/development process, used Test Rail/TFS/MTM for test case/defect Management
• Three week build cycle, 2 weeks functional testing, 1 week regression testing with smoke testing in staging.
• Developed automation for regression testing and productivity tools using Python/Selenium with JavaScript to control the DOM. Endtest.io was used as a server base to run regression test automation.
• Tested Android and IOS mobile systems, scanning equipment for the mobile phones, and internet cloud systems backend, Java Script frontend, and desktop. Use MySQL to verify database results of testing.
• Managed one person in QA department, and 2 testers on loan from New York during regression testing.
• Used MySQL to verify database changes, and Excel Google Docs to coordinate test plans, test issues.

Confidential, Boulder, CO

QA Automation Engineer/Manual Tester

Responsibilities:

• Worked in the Ad Technology department where I ran automation tests for regression about 25% of the time in the cloud (saucelabs) using the Jenkins build server as an interface to the automation tests. I created some automation tests using AppleScript with JavaScript objects.
• Manual Testing was the majority of my job focus where I was involved with testing video ad technology (VAST protocol, FLASH/HTML) and display ad technology using JavaScript synch and asynch tags with some mobile testing included.
• Involved in backend testing 70% of the time with the Ad Server called Blackbird.
• Used Curl commands to hit the Blackbird server directly to test the JSONP response.
• This was done in the MAC terminal as well as with PostMan. Verified ad activity in the Kafka logs, SqlServer database, and the Hive database server.
• Agile/Scrum development process using JIRA to track User Stories, test cases, and defects.

Clickfox Denver, CO

QA Lead / Senior Test Automation Engineer

Responsibilities:

• Lead a team of 5 American manual/automation test engineers and 5 Indian manual/automation engineers.
• I was relied upon to create automation scripts, manage the teams progress on their automation scripts, and verifying coverage of automation and manual tests for the CEA classic and CEA NewUI product lines. To manage the team effectively we set goals, objectives, strategies and tactics.
• We had sprint planning meetings for each sprint cycle.
• We deployed builds to VM’s for testing different branches and for testing the default branch.
• We used Selenium with Protractor and AngularJS as our automation tool. Our Versioning tool was Mercurial using Eclipse/IntelliJ as an IDE.
• We used TortoiseHG as a GUI front end to Mercurial.
• Our biggest challenge was to automate tests where the GUI didn’t change a lot, which were mainly tests associated with the direct functionality of the product.
• Communication was key across the whole team for reaching both manual and automation testing goals.
• Used Jenkins to control the automation test scripts so dev and QA could work and coordinate their automation efforts based on CI processes.

Confidential, Longmont, CO

Senior QA Automation Test Engineer

Responsibilities:

• Automated the SAP satellite tasking order system for regression testing using Confidential . This was end to end regression testing typically done after a hardening sprint.
• The Confidential framework consisted of a Jenkins interface to control builds/testing using many automation technologies such as JMeter, SoapUI, QLeTPChilkat, and QFTest. Subversion (SVN) was used to control the Confidential code changes among the group of automation engineers coding the scripts. Rally was used to track defects and user stories among the different
• QA groups. ALM 11 was used to track our test cycle results.
• The automation script was setup to run on 3 different environments: a QA environment, a development environment, and a secure environment.
• Automated Linux tests using a Perl framework that interfaced an Excel spreadsheet.
• This was done to test the secure transfer of data for both the high and low sides of a software guard system.
• Data was transferred through an interface in Linux (typically with large image products and associated meta data) to verify that the data was correctly transferred from the high secure side and then to the low secure side without difficulty or errors.
• This setup dramatically increased our testing coverage and made possible to meet the tight deadlines required by the Confidential to fulfill the Confidential contract Used the Agile software development methodology to consistently meet our build schedule.
• We created User
• Stories for the automation or manual testing to be done for each sprint and tracked our progress in Rally.
• The combination of manual testing with automation allowed us to triple our regression coverage with the same amount of people in our group over a period of 6 months.

Confidential, Westminster, CO

QA Automation Engineer

Responsibilities:

• Worked with Confidential add on BPT for automation testing for 50% of my time while running manual testing for the other 50% of my time.
• The testing was done on a product used by hospitals called "HED" that was created to track a patients drug usage and care.
• HED proved to be a very complex product to automate.
• It used Confidential directly with ALM 11 to manage the automation with the BPT add on that allowed manual testers to run automation tests.
• I was able to make a large amount of progress on the manual testing, but the automation regression testing was not fully developed, so only a few hundred tests were actually automated effectively.
• We used Rally to track our testing in an Agile environment along with Quality Center to hold our test plans and defects.

Confidential, Broomfield, CO

QA Automation Engineer

Responsibilities:

• Given the responsibility for creating an automation framework to automate their salesforce.com interface that tracked their Confidential virus detection software offerings to various customers for the Confidential salesforce team.
• A Confidential framework based on keyword entry into the default Confidential spreadsheets was created for use by ther automation engineers and manual testers.
• The time to test the salesforce.com interface was reduced from 1 hour to 5 minutes for each regression test.
• An Oracle ERP interface was also automated that completed the ordering process that worked with the salesforce.com website.