Senior Qa Lead Release Coordinator For Mcs(mobile Content Solutions) Alm Local Admin Sharepoint Loc resume example

Responsible for automating various projects across QA

• Automated around 50 test cases using QTP for major projects such as Voice over IP, Cable service, High Speed Internet with cable, based on use cases.

• Ran manual test cases prior to automating, for Client/Server, multi-tier Web applications, black box testing and complex SQL queries messaging for white box testing. Tested applications which are billing systems where a customer is provisioned with the requested services such as VOIP, digital cable, appropriate video equipments etc.

• Maintained project plans for QA, generated reports using Test Director.

Environment: Windows XP, Quick Test Professional 8.2, Test Director, Unix, Visual Basic, Java, Oracle 9i, MVS, Clear quest, MS Project

Responsible for quality of Transport Element Activation Manager Software.

• Installed, maintained and troubleshot test environment.

• Worked as a liaison between 2 teams, coordinating efforts for Inter-Product Testing.

• Performed new feature testing, blackbox, whitebox, verification and regression testing.

• Automated test plans using Silk Test created for multiple vendor network elements in parallel with testing effort. Also tested web-based gui using Silktest.

• Generated test plan from business requirements, which included traceablity matrix of the test cases along with mapped requirements. Held meetings for test plan inspections. Developed scripts for automation testing. Documented test results to be reviewed by test teams. Attended weekly meetings and provided test status. Worked with developers to ensure defects in system were corrected. Created modification requests (MRs) and assigned severity levels to them. Reviewed end-user and use-case document to ensure proper content according to software operations. Coordinated test activities for new features introduced in software. Developed a set of regression test cases. Gave demos/presentations to clients for the new features. Performed final regression test after final build. Was a major contributor during customer release notes revision sessions.

• Used VPN client/Citrix Server to access the applications remotely.

Environment: Windows NT/2000/XP, Silktest, Unix, Powerbuilder, Java, Oracle 9i, MVS, Adobe Framemaker, VPN, Citrix

Worked on projects such as TEAMS and MTS. TEAMS(Traffic Engineering and Management System) supports the ATM(Asynchronous Transfer Mode) network based on Cascade CBX500 switches. Teams produced backbone reports for internal customers on a weekly and monthly basis. MTS (Master Topology Server) provided current source of topology information for AT&T Operation Support Systems that support AT&T ATM Service.

• Created and reviewed the system and regression test plans for both Teams and MTS

• Executed the test cases, testing the reports like switch, trunk and network

• Constantly monitored hourly files for topology information and traffic measurements

• Tested backend and a gui based frontend

• Automated test plans using WinRunner and TestDirector

Environment: Solaris 2.5.1,Unix,Informix 7.24, WinRunner, TestDirector

Worked on a project called GPL(Group Personal Lines Insurance). GPL involved offering personal insurance policies for Homeowners and Automobile to a group of employees in any company. Involved in analyzing and mapping the data in accordance with the ISO(Insurance Services Offices). Files contained information for the check disbursements for claims and premium refunds.

• Analyzed and mapped the data (backend)

• Created test plans, test conditions and test script

Environment: Windows 98, Oracle

Involved in an Y2K project for a brokerage and investment banking application.

Environment: Windows 98, MS Excel, Visual Studio

Worked on DTM(Data Transport Manager) system used to transfer ledger files. DTM is a system designed to facilitate the General Ledger (G/L) feeder processes as Business Units migrate from current G/Ls to distributed Business Unit Ledgers.

• Created test schedule from start, test plans, use cases, test conditions and test script

• Executed system test, approved node test

• Automated front end testing using SQA Robot and back end testing using Unix Shell scripts

• Also held regular meetings on updates and schedules

• Involved in Y2K: analyzed both front and backend for dates, created matrices with the screen (front end) and function names (backend) and date references, created test schedule, plans, test conditions and test scripts

Environment: Unix, MVS, Sybase, Windows 95, SQA Robot

Worked on RESTM (Residential Telemarketing) system which is a very large multi-platform system. The orders are taken across all of the USA, 24 hours a day, 7 days a week. The system operated in on-line and in batch mode. On-line system is being used by AT&T representatives to take orders. The orders are also taken by a large number of authorized vendors, those orders come to the system through batch mode.

• Features included: Huge volume of data, very quick turn around time for modification and changes, lots of downstream feeds with a very rigid time commitments, complicated and strict business rules such as Third Party verification.

• Performed the analysis, coding and debugging. Created stored procedures, functions, triggers and views to implement business rules and maintain data integrity. Designed a menu based user interface for navigation to update the database. Used Developer/2000 to design reports for use at various levels.

• Carried out QA Analysis and Testing, which included Unit testing, Regression Testing and Backend Testing. Entered and tracked trouble tickets until each problem was resolved. Created and maintained test data and test environment. Checked the walkthroughs.

• Carried out Production Support which meant carrying beeper on a rotation to support the 24 hour production.

Environment: Windows NT, UNIX, WinRunner, Oracle 7.3, Developer 2000, VAX-VMS, C, Script, Powerbuilder, Report Writer, Lotus Notes

Worked on Windows based application called 'S&N' which runs on OS/2 environment using cleavers and TCP/IP connection to the host. The main responsibility was to test the various builds for the default flow status of the application and the OLP (On-Line Provisioning) status of the application. Default flows were used to establish: New Service, Disconnect Service, Move, Suspend/Restore Service.

• Analyzed and understood system requirements and planned the test based on those requirements. Was responsible for the approval of plans by the clients and users and created the test cases based on those.

• Created test data and test environment and scheduled the test executions.

• Executed the test carried out error reporting and tracking. Controlled the production environment by allowing only the tested modules to be copied down.

Environment: Windows 3.11, OS/2, Lotus Notes

Worked on Access Ability which ran on OS/2 as client and AS/400 as server.

Testing Methodologies:

• The Analyst prepared the system requirements

• QA group and Developers received a copy of the requirements

• Test plans and test cases were developed based on the requirements

• The test plan included details of the following:

1. Unit testing (a single module functionality) plans

2. String testing (few relevant functionality) plans

3. Stress testing (Negative testing) plan

4. System testing (in totality) plans

5. SQL Scripts to test the backend database.

Each of the test scenarios were documented with expected results and the severity level in case of failure e.g.severity level '1' = fatal error, '2' = Conditon and '3' = minor

The test execution schedules were prepared along with the sequence of operation

Enviroment:OS/2 as client and AS/400 as server.