TECHNICAL SKILLS:

Languages: C, Java, PERL, XML, shell, Python, AppleScript

IDE: Eclipse, Android Studio, IntelliJ IDEA

Database: SQL, Postgres

OS: Linux, Apache Tomcat, Ubuntu

Builds: Apache Maven, Apache Ant, Gradle

Platforms: Android, USSD, Windows, Macs, Internet Explorer, FireFox, Safari, IPTV, DVR, Set - top Boxes

Testing: Black Box, Grey Box, White Box, API-testing, Video On Demand, IPTV, DVR, N-tier, Automation, Load Testing, Android Devices, Web Portals

Automation: Uiautomator, TestNG, SilkTest, home-grown Java tool

Documentation: Wiki, Assembla, Jira, Excel, SVN , TestRail

Other: Gerrit, Jenkins, adb

PROFESSIONAL EXPERIENCE:

Sr QA Engineer

Confidential, San Jose, CA

Responsibilities:

• Responsible for arriving early every day to put the day's android OS build on Jenkins through smoke test (manual). Used adb to install applications. Opened defects as necessary, and sent out smoke test result report to others on the QA team.
• Defects were opened, containing screenshots and logs, along with assignments to relevant developer, assigning severity, and giving test environment info.
• Developed the test cases in TestRail. Later executed the test cases, noting the test environment used, and a pass or a fail. Defects opened in Jira as necessary.

Test Engineer

Confidential, Sunnyvale, CA

Responsibilities:

• Designed and created test case strategies and test cases in the features owned by the Jobs team; mostly web-server API test cases.
• Developed the test cases in Java on a Linux desktop, within the IntelliJ IDEA IDE, for an existing TestNG automation framework.
• Continuous Integration: test cases would be run automatically within a Hudson system nightly. I would investigate any failures to pin point the root cause from logs or from code. I would then report my findings to development. The findings would determine whether a build should be released.

Sr. Quality Assurance Engineer

Confidential, Sunnyvale, CA (contract)

Responsibilities:

• This was a contract through Confidential Consultants to replace someone on maternity leave.
• I worked in the department that delivers a home screen app for android phones.
• Typically I did a manual test in the morning of the last night's build. Then the rest of the day I would document new test cases, and create automation test scripts for uiautomator, using Android Studio. Skills used: Android Studio, Uiautomator, Java, Gerrit, Git, Python

QA Engineer

Confidential, Mountain View, CA

Responsibilities:

• Wrote test plans and test suites for an android app, the product's agent web-portal, database (SQL), API-server, and server load tool.
• Opened complete tickets in tracking system (Assembla) after investigation via logs, database, and code base. Proposed fix to developers. After fix was in, verified fix and closed ticket.
• For the android app and API server, if the fix was rudimentary, checked-out code (SVN), created own build (Apache Maven or Ant), installed build on android or on test server, tested, went through review of my code (Java), and then checked in code after having another QA Engineer verify the fix.
• Created and maintained virtual machines (Ovirt) for test servers. Logged in to servers (Linux), and installed war files to server (Apache tomcat), then booted-up tomcat. Monitored logs for issues.
• Wrote automation test script (PERL) for doing API testing.
• Conducted investigation for a load tool to purchase. Found none suited our needs, so I wrote my own load tool over the weekend in Java. Executed load testing.
• Made periodic database backups. Was going to create a shell script to run a cron job to automate backups, but Boom lost it's financing before I could do that.
• Was test lead for QA in Haiti office.
• Created web pages on a wiki for documenting server maintenance, server installation, test plans, etc.
• Participated in daily standup meetings.
• Localization testing: learned how to read and translate some Haitian Creole along the way.: -)

QA Engineer

Confidential, Redwood City, CA

Responsibilities:

• Created Selenium test cases and test suites from scratch.
• Gave a presentation and demo of Selenium IDE to engineering staff.

Test Engineer

Confidential, Redwood City, CA

Responsibilities:

• Tested devices (alarm sensors and system panels) for adherence to specs and manuals.
• Verified portal functionality in all aspects from installation and upgrade of equipment.
• Wrote hundreds of test cases hub features (the hub allowed for wireless cameras and touch screens) along with existing devices. Executed test cases. Wrote bug reports, verified fixes .
• Used to create and maintain test cases, along with opening bug reports for defects found.
• Used to manage bug reports.

QA Engineer

Confidential, Cupertino, CA

Responsibilities:

• Browsers (IE, Safari), OS (Windows, OS X), mobile devices (iPhone, iPod).
• Tested for macro-blocking, pixelation, mosquito noise, ringing, audio/video sync, etc.
• 3gp, 3g2, mov, mp4, m4v. Closed captions, movie info, etc.
• Repaired existing test suite of AppleScript tests. Ported the scripts to run both with QuickTime Player 7 and QuickTime Player 10. Created new test scripts to expand testing coverage.
• Managed test bed of PCs and Macs. All platforms would be re-imaged twice weekly for new builds.

QA Engineer

Confidential, Mountain View, CA

Responsibilities:

• Tested for macro-blocking, pixelation, mosquito noise, ringing, audio/video sync, etc.
• Used queries for data validation, sometimes data modification .
• Negotiated bug priorities.
• Created test bed of video assets, so that there was a minimal set of assets for total test-case coverage. Created a Confidential Excel spreadsheet to provide an overview of the test assets, listing the video meta-data, video coding standard and the related test cases.
• Installed releases on video servers. Deployed video assets.
• Created guidelines for creating video assets and for installing releases on servers.

QA Engineer

Confidential, San Jose, CA

Responsibilities:

• Used queries to verify that bid and auction information were as expected .
• Used a proprietary white-box automation tool which required using XML, both to create auction listings in a database and to simulate auction or user events to those listings.

QA Engineer

Confidential

Responsibilities:

• Tested for macro-blocking, pixelation, mosquito noise, ringing, audio/video sync, etc.
• A udio and video players.
• Tested player controls, ad banners and related links.
• Verified proprietary players conformed to industry standards.
• Tested media players on these platforms.
• Troubleshooting and white-box testing in these languages.
• Executed load, stress, performance and memory leakage tests .

QA Engineer

Confidential

Responsibilities:

• Evaluated various automation programs before settling on SilkTest.
• Designed an automated test environment; wrote, executed and maintained scripts in order to automate smoke, regression and server-side testing.
• Maintained test matrices and benchmarks.