Software Test Qa

Steven Linde

Imperial Beach, CA 619-***-**** *************@*****.***

Summary

Twenty years of experience in Test & QA Management, QA & Validation Engineering. Which includes, Test and Development Analysis, Software Test Metrics, Creating software test process and standards, QA & Validation, design, write and implement software test plans, design, write and implement test procedures, as well as design and implement software automation processes and standards.

QA/Test Management Experience – 6 years

QA/Test/Validation/Automation/Performance Lead Experience – 14 years

Skills

Software Test/ QA / Validation Management: Personnel Resource Allocation & Analysis, implement process - IEEE, CMMI, as well as ISO. Analyze data from verification and reliability test for conformance to pre-determined acceptance criteria and prepare formal reports and results summaries, Assist engineering team with root cause analysis for problems identified during verification testing.

Software Models(SDLC): Agile Scrum, Waterfall, KANBAN.

Defect tracking: Bugzilla, Jira, Clarify, Rally, TFS

Config. Mgmt: Perforce, Tortoise SVN, GitHub, CVS, TFS, Visual Source Safe.

Languages: C#, VB, Python & WxPython, JavaScript.

Automation Tools: Quick Test Pro (UFT), Selenium Silk Test, Cucumber (Gherkin), Test Complete, DataDog, Ranorex, and others.

Performance Tools: Webload, Load Runner, Silk Test, JMeter

Test Management Software: Quality Center (ALM), JIRA Xray, QTest, Visual Studio Test Management (TFS), Rational Quality Management

Test Documentation: Test Strategy, Functional Design, Requirements, Resource Tracking, Test Plans, Test Procedures, Test Metrics, Cost Analysis, Software Procedures and Standards and Automation Processes and Procedures.

Types of Testing (not limited to): Validation (FDA), Verification (FDA), Verification and Validation (FDA), Verification and Validation (DOD,) Reliability, Web based and desktop applications to include: Unit, functional black box, white box, negative, integration, system, performance, stress, and stability.

Automation Frameworks Built

1.Instride.com –

a.I worked with the Infrastructure team to build a new CI/CD kubernetes pipeline for microservices. The Company was focused on all new APIs would delivered using microservices. The microservices were pulled from GitHub and using selenium or another tool such as postman, sent through the pipeline. Ideally, we were moving towards being able to set it up where the manual leads would be able to use it to tools, select the service and send it through the pipeline.

b.Enhancing Jenkins CI/CD frameworks with Jenkins Test Automation and using Linux Selenium and BDD Cucumber/Gherkin breaking down test scripts into Smoke Test (scripts), End-to-End (Scripts), Light Regression (Scripts). Everyday morning we ran our smoke test script, once a weeks we ran our E2E and Light Regressions Scripts. We used Jenkins Test Automation which allowed us to capture metrics by percentage for pass / fails and we could also look to see what actually failed.

c.I began moving the team from BDD to TDD.

2.Illumina – They were using a BDD Cucumber/Gherkin Framework using selenium and JavaScript. This was cumbersome for the product the organization was using. I moved them to HP ALM (Quality Center for Test Case Management and Quick Test Professional for Scripting (VB)). We continued to use the Cucumber scripts and maintain them, however moved forward with all new scripting using ALM.

3.Ntrepid –

a.The Company had HP ALM when I started and demanded I use it. However, Quick Test Professional (QTP) didn’t support JSON which they used.

i.I developed QTP script in VB that could be used for each test case; you would have to attach the test case ID from Quality Center.

ii.I developed a script for each test case, API JSON, which was called by the VB script.

iii.Quality Center Test Case Manager had open source API’s.

1.I developed calls in python for pass and fail which could be used when called to pass or fail a test case in Quality Center within a script.

iv. If a script passed it would make call the Quality Center API for pass and update the respective test case in Quality Center with Pass.

v.If the script failed it would make call the Quality Center API for fail and update the respective test case in Quality Center with Pass.

b.I created two desktop applications using wxpython that bypassed QTP and you could execute the scripts and they would update Quality Center.

4.Nirvanix

a.I built a C# desktop application with a built in browser to test the API’s for Nirvanix’s Cloud based platform prior to executing performance testing.

b.I wrote JavaScripts for Webload for performance testing.

c.I used DT (Data Test) and incorporated it into perl scripts for additional performance testing.

Experience

Instride.com (Remote)

Los Angeles, CA

Software Automation Lead (Sr. SDET) February 2022 – September 2023

Lead a team of 11 Automation Engineers

Used JIRA XRAY Test Manager to manage stories for automation.

Used QTest Test Manager to manage Stories for automation.

We used Jenkins Test Automation integrated with GitHub to run all of our automation.

oJenkins cluster into a Selenium Grid3 cluster and carry out tests on the heterogeneous Jenkins clusters.

oUse a Linux Selenium Framework.

oAutomation Test Cases written using Cucumber > Gherkin Framework.

oAutomation Test Cases included frontend, API and Microservices.

oEverything written in JavaScript (JS).

I created, implemented and wrote procedures for Software Automation Strategy.

I moved the team from KANBAN to Agile Scrum to get better control over the metrics.

Determine the QA issues, gaps, test case writing that affected automation.

Moved the automation team from XRAY to QTest Test Manager.

oFrom that point the manual test team would be using QTest to write Test Cases.

oThe automation team would no longer user XRAY and use QTest.

oHowever, there was a 1300 automation test case backlog I found. The automation team still has to move between the two platforms.

Use Scrum Board in JIRA to track each sprint. Each sprint was two weeks in length.

Agile process, product backlog, sprint backlog, grooming, pre-sprint planning, sprint planning, mid sprint reviews, retrospective.

Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

In April 2022 I identified a 1300 backlog in JIRA. As of September 2023 it was 100% automated.

Between February 2023 through September 2023 we were 100% automated in QTest, while still completed automating the test cases in JIRA

Helped create a new CI/CD pipeline for Micorservices and implement throughout the organization.

Reason for leaving: The positon was outsourced.

NCI (Remote)

San Diego, CA (Remote)

Test Director March 2022 – December 2022

The Director of Test Engineering for the DIGIT (Digital Innovation for GSA Infrastructure Technologies) contract.

Provided overall leadership of the Test and Evaluation (T&E) tasks and served as primary liaison to the Government for supporting contract coordination and task execution

Designed and developed advanced test programs, processes, and systems to measure the functionality and integrity of products and services

Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

Managed T&E resources and tasks; ensured quality assurance of test processes and products

Drove innovation and responsiveness to program changes and evolving T&E status to help manage program risk; developed alternative courses of action, workarounds, and fallback positions with a recommended course of action for each risk, and monitors and re-evaluates risks at appropriate milestones

Designed and built test stations

Wrote advanced highly complex test procedures and protocols to assess product reliability and evaluated the ability of products to meet performance standards and specifications

Monitored the gathering of test data and supervised the evaluation of test results to determine if product designs and architecture meets customer specifications and performance expectations

Developed advanced highly complex test simulations to evaluate how products react under different conditions and analyzed product failure to assess the integrity and reliability of product performance

Defined debug protocols for test hardware and software

Analyzed complex test cases and scenarios and reports results

Collaborated with other engineering groups and improved or upgraded product performance

Provided technical consultation to other organizations and work leadership for lower level employees

Provided architectural and system/software engineering solutions to develop or integrate products and applications intended for use by the customer's system developers

Applied qualifications to data elements

Trained QA Staff on Selenium Python Scripting.

Reason for leaving: Laid off. NIC reorganized and became a different Company.

Modular Medical, Inc

San Diego, CA January 2020 – March 2020

Sr. Software Quality Assurance & Validation

Research and development of a new type of wearable affordable insulin pump for diabetics a Class 3 product.

I created a Software Development and Design Validation & Verification process using KANBAN SDLC Methodology to be used in for FDA submission and processes.

To included software development processes beginning with the creation, approval and tracking of requirements, through the Software Development Plan, to the Software Design Document and Software Architecture Document.

I designed and implemented Integration, Verification and Validation of the product within the confines of the SDLC.

I also created the Project Management processes used to track and manage each project. !

I was instrumental in creating various Risk Assessments;

I created the Software Configuration Management Plan and reviewed and had input on all Quality Assurance SOPs.

Successfully created Software Quality Assurance Processes that met the following standards:

oGuidance for the Content of Premarket Submissions for Software Contained in Medical Devices.

oGAMP5

oFDA Guidance for Software Validation

oTIR36:2007 Validation of Software for Regulated Processes.

oIEC 62304 Medical Device Software

o21 CFR 820.70 (i) Production and Process Controls – Automated Processes.

o21 CFR 820.30 Design Controls

o21 CFR part 11 Electronic Records, Electronic Signatures.

o21 CFR Part 820 Quality System Regulations

oCAPA / Defect / Deviation Management.

oIQ/OQ/PQ

Created templates for Software Development and Verification and Validation to include:

oSoftware Development Plan (SDP), Software Requirements Specification (SRS), Software Design Document (SDD), and Software Architecture Documents (SAD).

oVerification and Validation Master Test Plan, Software Test Case Traceability Matrix for both Verification and Validation, Software Installation Qualification Test Protocols for both Verification and Validation,, Software Test Protocols for both Verification and Validation, Software Test Summary Reports, Software Installation Qualification Test Protocols for both Verification and Validation.

Created, wrote and implemented the Software Development Life Cycle (SDLC) for KANBAN.

Wrote and executed SDP’s, SRS’s, SDD’s, SAD’s.

Developed and worked on processes for QMS. I was also instrumental in researching eQMS, reviewing and testing potential systems to be used.

Wrote and executed all V&V documents.

Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

Reason for leaving: The organization closed/shutdown due to the pandemic.

Invivoscribe

San Diego, CA January 2019 – May 2019

Senior Validation Engineer

I lead the company in the Verification and Validation of their LIMS product STARLIMS. STARLIMS is an open source product which allowed Invivoscribe to modify it to meet their needs.

FDA Class 2 product.

Supervise one Validation Engineer

GAMP5 for Medical Devices, ISO 13485 QMS for Medical Devices

FDA Guidelines for Software Validation

Created V & V Master Test Plan, Test Protocol, Test Report and Deviation templates.

Implemented Agile Scrum SDLC throughout the Development team.

Responsible for developing and delivering validated tools, compliant platforms and solutions in coordination with cross-functional teams in an FDA environment.

Led and oversaw design verification and validation procedures for software, products, systems, equipment and other IT infrastructure throughout life cycle phases.

Authored Test Protocols / test cases based on provided software design specifications utilizing both positive and negative testing processes.

Created required project deliverables related to testing: test plan, test procedures, test scripts and completed acceptance test/test reports.

Led the execution of Master V &V Test Plans, protocols and manages deviations.

Led drive to include CI/CD into the SDLC.

Wrote and executes IQ, OQ and PQ.

Communicated all observed defects to the technical lead, updates test cases based on the discovered defects and re-executes test cases accordingly.

Responsible for change and configuration management activities by managing and documenting change requests, performing software change impact analysis and regression testing for Quality Management Systems (QMS) and Information Technology (IT) systems.

Collected Test Metrics such as defect attrition rates, number of test cases executed – Pass/Fail, defect attrition rates over x number of test cycles to determine the releaseability of the software and present those findings in the Test Report.

Database / SQL testing.

CAPA / Defect/ Deviation Management.

Root Cause Analysis

SaMD

Used Intellect eQMS.

Reason for leaving: Moved to another organization.

Illumina

San Diego, CA August 2018 – January 2019

Contract Position

Senior Test Engineer / Lead Automation Engineer

LIMS (Laboratory Information Management System). This was a LIMS that they built themselves to be used internally.

A FDA Class 2 product

Supervise three Test Engineers

Wrote Software Test Process and Standards

oSited FDA Guidelines for Software Validation

oSited LIMS SDLC

oSited LIMS Qualification

Wrote Software Automation Processes and Standards

Primary automation tool used is HP QC (ALM) and QTP (UFT) for functional testing. They also used Cucumber>Gherkin as well as Selenium (JavaScript).

Primary tool used for Performance, Load and Stress testing was JMeter and Load Runner.

Proposed Defect Management process using JIRA.

Identified SDLC software methodologies for them, switching them from Waterfall to Agile Scrum.

Worked to help them move forward with QA processes and worked with the QA Engineers.

Implemented processes with GAMP5 for Medical Devices, ISO 13485 QMS for Medical Devices.

Implemented FDA Guidelines for Software Tool Qualification.

Database / SQL testing.

Used Jira to manage defects.

Led drive to include CI/CD into the SDLC.

CAPA

Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

Defect / Deviation Management.

SaMD

SAP QA for their eQMS.

Reason for leaving: Contract ended.

SAIC / NASA (Remote)

San Diego, CA April 2018 – September 2018

Contract Position (Ends August 2018)

Quality Assurance Manager

Helped Drive Team through CMMI Processes, ISO 9000/9001 & IEEE

Wrote the overall Quality Assurance Plan which helped drive configuration management, project management, development, security and test.

Wrote NASA Web Services Quality Assurance and Testing Plan

Wrote NASA Web Services Test Plan Template

Wrote NASA Web Services Test Procedure Template

Wrote NASA Web Services Test Results Summary Template

Wrote NASA Web Services Automation Processes and Standards

Wrote NASA Web Services Defects Management Plan

Helped Senior Management implement Agile Scrum Processes and Procedures

Led drive to include CI /CD into the SDLC.

Reason for leaving: Contract ended.

Hewlett Packard Enterprise

San Diego, CA June 2015 – October 2017

Verification and Validation Manager/Lead

Create and implement IEEE/ISO Test Plans and Procedures.

Create and implement formal Defect Management Process.

Implement Agile Scrum / KANBAN processes in test.

Used TFS to manager Epics, features, story’s, and defects.

Manage over twenty-eight test projects on a continuous base.

Manage teams from two to ten people.

Create, write and implement QA Automation standards and procedures.

Evaluate QA/Test Automation tools and implement them.

oUsed Ranorex and Selenium.

Train Project Owners, Project Manager and Engineering Groups on Test Processes and documentation.

Types of testing executed – Black box, Scenario, performance.

Used Rational Quality Manager to manage test cycles.

Created test scripts from test cases using Java.

Tested in Windows and Unix environments.

Led drive to include CI /CD into the SDLC.

Collected Test Metrics such as defect attrition rates, number of test cases executed – Pass/Fail, defect attrition rates over x number of test cycles to determine the releaseability of the software and present those findings in the Test Report.

Worked / Tested in Windows and Unix environment’s.

Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

Held Secret Clearance.

Reason for leaving: Laid off – Navy Contract was ending.

Ntrepid

San Diego, CA Feb. 2012 – January 2015

Software Automation Lead

• Wrote and implemented Test Plans and Test Procedures.

Collected Test Metrics such as defect attrition rates, number of test cases executed, defect attrition rates over x number of test cycles to determine the releaseability of the software and present those findings in the Test Report.

Create Automation Test Framework from ground up using HP Quality Center (ALM), Quick Test Pro (UFT) VB and Python to design and implement software automation architecture, processes and standards.

• Create automation processes and standard

• Create QTP/UFT scripts using descriptive programming

•Create QTP/UFT scripts using a combination of record and playback and descriptive programming.

•Create Python scripts for Web Services API testing.

•Created Python desktop applications.

•Created a Python module which linked the python test scripts to Quality Center and update it with pass/fail and actual results.

•Software Methodology: Agile Scrum

•Database / SQL testing.

•Web service REST API, Web based and desktop application automation.

•Led drive to include CI/CD into the SDLC.

•Tested in Windows and Unix environments.

•Used JMETER for Performance, Load and Stress Testing.

•Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

•Reason for Leaving: Laid off, the Government cut back on funding.

Miro Technologies

San Diego, CA

Product Test Manager June 2011 - Feb. 2012

•Leading a functional test team of 10 software quality analysts.

•Types of testing done – White, Gray and Black box, SQL, Oracle, regression, performance.

•Design and implement the company’s quality processes and standards.

•Design and implement Test Plans and Test Procedures.

•Collected Test Metrics such as defect attrition rates, number of test cases executed, defect attrition rates over x number of test cycles to determine the releaseability of the software and present those findings in the Test Report.

•HP Quality Center (ALM) to manage test cycles.

•HP Quick Test Pro (UFT) for software automation.

•Wrote Automation Processes and Standards documentation.

•Used Load Runner and JMeter for Performance, Load and Stress testing.

•Software Methodology: Agile Scrum & Waterfall.

•Web-based testing and automation.

•Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

•Scheduling test cycles.

•Reason for leaving: I left for a different organization.

Nirvanix

San Diego, CA

Sr. Load (Performance) Engineer June 2008 - March 2010

Created Automation Test Framework from the ground up using MS Visual Studios C#.

Used Selenium C# for functional automation testing as well as Data Test.

Execute performance, stress and load testing in a networked multi-tiered environment using Web Load, language used was JavaScript.

Design & Implement test processes for performance, stress, and load for cloud storage environment.

Wrote and implemented Performance, Load and Stress Test Plans and Test Procedures.

Collected Test Metrics such as defect attrition rates, number of test cases executed – Pass/Fail, defect attrition rates over x number of test cycles to determine the releaseability of the software and present those findings in the Test Report.

Created C# desktop applications for functional testing.

Created shell and Perl scripts for the testing of the REST API's.

Worked / tested in Windows and Unix Environments.

Software Methodology: Agile Scrum

Designed & implemented software test plans and procedures.

Wrote SQL queries for test purposes.

Wrote Automation Process and Standards documents.

Used Jira to manage Epic’s, User Stories, Technical Debt, Impacts and defects.

Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

Reason for Leaving: The Company closed.

Mitchell International

San Diego, CA

Quality Service Manager. Nov. 2006 - Jan. 2008

• Lead a functional test team of 15 engineers.

• Lead an automation team of 3 automation engineers.

o Automated desktop and web-based applications using QTP (UFT) and Test Complete.

o Design & implement Automation standards and processes.

• Managing multiple projects.

• Create work estimates, write and implement test plans.

• Cost analysis:

o ROI on automation tools.

o Defect Metrics.

o Personnel resources.

o Cost overruns to projects.

• Software Methodology: Waterfall

• Development in Software QA Architectures.

Wrote Automation Process and Standards documentation.

Collected Test Metrics such as defect attrition rates, number of test cases executed – Pass/Fail, defect attrition rates over x number of test cycles to determine the releaseability of the software and present those findings in the Test Report.

Risk Analysis, Resource Allocation, Root Analysis with cause and effect, Risk Mitigation, Incident investigation, and Solution resolution.

• Scheduling

Reason for leaving: I resigned

Overland Storage

Senior Test Engineer (Lead) July 2004 – October 2007

San Diego, CA 92123

Reason for leaving: Laid off, Company lost 2/3’s of revenue.

Intel Corporation

Senior Test Engineer (Lead) January 2000 – February 2004

Network Equipment Division

San Diego, CA 92128

Reason for leaving: Laid off, division closed.

Education

Coleman University – Associate’s Science – Computer Engineering

San Diego City College – General Education

San Diego State University – Computer Science

US Army Schools

Contact this candidate