SUMMARY:

• More than 9 years experience in mainframe, UNIX, web, and client server applications.
• Manual and automated testing involvement includes test planning, test design (from requirements) and test execution/validation/reporting.
• Having development experience allows me to relate with developers easily.
• Recently completed (9/26/2016) a course from ISC2 in order to expand my knowledge in software development and to bring my skills up to date after a long time of recuperation.
• The class is CSSLP and it focused on cyber security in the SDLC.

TECHNICAL SKILLS:

SOS: UNIX, Vista, XP Windows 2000, NT 4, Windows 9X, MVS, VM CICS

Languages: COBOL, JCL, SQL, C TSL, JavaScript, VB

DBMS: DB2, MSQL 5.6, 7.0, 2000, ORACLE, ACCESS, INFORMIX

Tools: WinRunner, LoadRunner, QTP, ROBOT, XDE, Functional Tester, RUP, ClearCase, Quality Center, Test Director, Test Manager, EZtrieve, File Aide

Other: IIS SourceSafe, Tibet, TestTrack, Vantive, ClearQuest, Remedy, CVSCSSLP from ISC2

PROFESSIONAL EXPERIENCE:

Confidential, Anthony,Texas

QA Analyst

Responsibilities:

• The Confidential application uses a data map to allow similar but different applications to be used by the host business.
• A good example would this business that handles mortgages.
• Several vendors with similar but different data sets that are submitted to the lender can be processed by one application.
• I was tasked at first to manually examine the data mapping of the three vendors assigned to me.
• Any discrepancies were discussed with development and if found to be a bug were logged accordingly.
• I then created test data XML files for each vendor.
• I would submit a test XML file via an SQL script and after processing compare the test XML file to the processed file.
• Any problems were dealt with between development and QA.

Confidential

QA Analyst

Responsibilities:

• Application used by a sales force for tracking business contacts information, and sales appointments.
• I was tasked with a part of the application the was a version of Microsoft Outlook.
• It was different in several ways making it unique.
• I was notified of updates, andwould test the changes and perform a regression test.
• I used vmware with OS images in order to test three versions of Windows at once.
• Write test plans. Write test cases from use cases and requirement documents.

Environment: Microsoft Windows Vista, XP, Win 2003 Agile methodology.

Confidential

QA Analyst

Responsibilities:

• Web page environment for major airline. Four different database used for test environment.Write test plans.
• Write test cases from use cases and requirement documents.
• Automate regression testing using Mercury Quick Test Pro.

Confidential

QA Analyst

Responsibilities:

• Write test cases from use cases and requirement documents.
• Automate regression testing using Mercury Quick Test Pro.
• Implement a performance test program using LoadRunner.

Environment: Microsoft Windows

Confidential

QA Test/ Systems Analyst

Responsibilities:

• Create test plans, directed the testers, verified the written test cases covered the application requirements, create a test case tracker and defect tracker using Excel.
• Confidential had been using a healthcare application from QCSI called QMAX.
• They updated to the QCSI application QNXT.
• To make the change over less confusing it was decided to process any Medicare files by them selves.
• My duties include running the interface process, documenting all issues, managing the Schaller testers, as well as the outside vendors, to ensure all problems are fixed and tested.
• As a system analyst I wrote requirement and design documents.

Environment: Microsoft .Net Framework Confidential, large group of end user base, three individual regions.

Confidential

QA Analyst

Responsibilities:

• I wrote test plans to manually test a software application that performs both domestic and foreign money transfers.
• Mapped files strings of data were created using Ultra Edit, these were entered into the UNIX system using the VI editor.

Environment: UNIX based banking system concerned with foreign and domestic banking process.

Confidential

QA Analyst

Responsibilities:

• I was tasked to create automated test scripts utilizing test cases written by the SRP user group.
• This approach involved a fair amount of interaction between me, and the various end users.
• This was done in order to make the test cases more robust and in turn make my test scripts more comprehensive.
• These test scripts were used on the web application currently in use at SRP.

Environment: IBM Mainframe, TSO, MVS, automation using Rational Robot for all areas of electric power company application.

Confidential

QA Analyst

Responsibilities:

• Performed manual testing on a mainframe in an MVS environment.
• Wrote Test Plans and Test Cases.
• I created test data files using FileAide, I wrote the JCL that used the test data in a batch job.
• After the batch ran, the results were reviewed and any problems were discussed with client services.
• As a business analyst, I performed mapping of requirements to detail design documents.
• Part of the business used a UNIX box, mapped file strings were created and entered using the VI editor.
• The process was run and results were validated.

Environment: IBM mainframe, TSO, MVS, Solaris UNIX running test cases on three different test regions.

Confidential

Web Tester

Responsibilities:

• Manually tested a web based application on a UNIX platform. Test data enter using the VI editor.
• Utilized Test Director as test case repository, and a data source for reporting.

Environment: UNIX, WINDOWS 2000, INFORMIX

Confidential

QA Analyst II

Responsibilities:

• Wrote test cases from a requirement document for a web based module.
• Wrote test plans, sizing documents using information and requirements gathered from the business analyst and development.
• Performed manual testing, both black box and white box, using the client based application, and tested the daily upload file to the main frame using a CICS test region and EZtrieve.
• Developed automated test script using RobotJ, XDE, Functional Tester, and Test Manager.
• Tested Java Code. Participated in developing performance tests cases using LoadRunner.
• Reported and tracked defects using ClearQuest.
• I worked with development and the DBA group to implement using ClearCase instead of the spread sheets being used for change control.

Environment: WINDOWS NT4, ACCESS, MSQL 7.0/2000, DB2, ORACLE, ROBOT, Functional Tester, ClearCase, ClearQuest, XDE, TEST MANAGER, IBM OS 390, MVS