Quality Assurance Analyst Resume
2.00/5 (Submit Your Rating)
Itasca, IL
CAREER SUMMARY:
Demonstrated efficiency in managing multiple assignments. Considered as a highly motivated individual with the ability to make informed decision based on analytical skills. Successfully completed various projects with emphasis on providing quality and accurate results.
WORK EXPERIENCE:
Confidential, Itasca, IL
Quality Assurance Analyst
Responsibilities:
- Business Requirements’ analysis, prepare test plans, user scenarios & test cases, test execution and defect management
- Help the Video teams to test GGV (GogoVision) in all browsers and devices
- Work with middleware team Foundational and PSG (Purchase Service Gateway)
- Assist other team members with information, technical support and dependencies
- Coordinate testing efforts with Project Managers/Scrum Masters and cross functional Engineering, Business, IT teams to assure required scope and guarantee test coverage
- Apply proven analytical and problem - solving skills to support testing process improvements, develop testing data/assets and contribute to Test strategies
- Use Jira to update Stories with tasks and communicate with all agile team.
- Use ALM QC and Jira to open, assign and track defects.
- Give updates during scrum team stand ups
- Supports End to End testing tasks to assure functional accuracy, quality, and adherence to Confidential IT & Business standards; for ultimate customer satisfaction/User Experience
- Create, track, maintain and execute automated test scripts in SoapUI.
- Plan and configure quality assurance infrastructure to support test efforts in multiple test environments SIT1/SIT2/SIT3/RITE.
- Work very closely with developers and product owners to update Acceptance Criteria in Jira and troubleshoot and investigate any issue.
- Use Sumologic and access the server box to get the log files
- Work very closely with infra during deployments and run health check after each deployment.
- Help in and mentoring of new hires
- Provides vision and inspiration to peers and subordinates
- Gives authority to work independently
- Responds well under pressure
- Admin for HP QC 10.0 and ALM QC 11.5 for various teams, maintained project and users in QC tool, create workflow scripts to assure the needed functions.
- Coordinate with Jira support to sync defects from ALM QC to Jira using Jam tool
Confidential, Hoffman Estates, IL
QC Tester/Test Architect
Responsibilities:
- Write Test Plan (System Test Package) and Test Cases based on the documents provided by Requirement and development teams (Business Processing Rules, System Requirements, High Level Design, Application Interface Design and Design Package).
- Use QCTT (QC Tracking Tool) to check workload and projects assignments.
- Review Test Plan Package with Project Manager, development team and requirement team.
- Perform Shakeout Testing, Sanity Testing, Functionality Testing, Regression Testing, System Testing, Positive and Negative Testing
- Create automated scripts in Parasoft SOAtest Perspective in Eclipse SDK.
- Responsible of creating and updating the database tables for all CSI (Common Service Integration) services.
- Use SQL queries to retrieve data from tables in database.
- Write XML Scripts for testing using Eclipse Integrated Test Environment (ITE) tool.
- Use MMT (Middleware Management Tool) to confirm the deployment of the services bundle and adapters bundle in QC environments.
- Validate the field mapping between private and public XML schema using Contivo Analyst tool.
- Use Toad DBA Oracle schema browser and SQL editor to view, retrieve and filter data from tables.
- Use Altova XML Spy to open XML files and view the schema structure.
- Use Splunk to view the log files and verify all the hosts and sources involved in the transaction.
- Use UNIX platform (PuTTY) to manually log in to the server and view the logs files.
- Identify defects early in the Software Development Life Cycle and assign them to development team.
- Use HP Quality Center and Rational ClearQuest to open tickets and report new defects and issues.
- Use BMC Remedy ticketing tool to open ticket for all the environment issues with EEM (Enterprise Environment Management).
- Use Q Messenger Meeting Room to troubleshoot issues with development and requirements teams.
- Use Hudson to execute production validation Job and report issues during production support.
Confidential, El Segundo, CA
Test Lead
Responsibilities:
- Create Test Plan, prepare Test cases according to the business specification and write test scripts and maintained them.
- Implement the whole life cycle of QA methodology starting from planning, capturing, creating, executing, reporting and tracking the defects using Quality Center.
- Host and attend meetings to review the Test Plan and to troubleshoot and investigate any issues captured during execution.
- Perform Functionality testing using integration and standalone C3.
- Use XML Maker spreadsheet to generate the XML script to run in C3 data driven or Legacy and manually analyze the BOM XML returned.
- Use HP Quality Center to track the Test Cases execution status and to open tickets and report new defects and issues.
- Use SOAtest to test Services for Legacy that don’ Confidential have a User Interface and manually analyze the generated XML.
- Conduct Smoke Testing in production environment for build verification.
Confidential, Hoffman Estates, IL
QC Tester
Responsibilities:
- Write Test Plan and Test Cases based on the documents provided by Requirement and development teams (Technical Requirements, High Level Design, Interface Agreements and Detailed Designs)
- Perform Sanity Testing, Smoke Testing, Functionality Testing, Regression Testing, System Testing, Positive and Negative Testing
- Write TSL Scripts (XML Scripts) for testing using the Integrated Test Environment (ITE) perspective in Eclipse SDK.
- Identify software defects early in the Software Development Life Cycle so that they can be resolved early.
- Use NetMeeting to Host meetings.
- Use HP Quality Center to track the Test Cases execution status and to open tickets and report new defects and issues.
- Use UNIX platform (PuTTY) to manually log in to the server and view the logs files.
- Use Toad DBA Oracle schema browser and SQL editor to view, retrieve and filter data from tables.
- Use Q Messenger Meeting Room to troubleshoot issues with the involved parties.
- Conduct Smoke Testing in production environment for build verification.