TestingCOE

Customer asks the test team to create the ticket for the testing request rather that creating one themselves Customer asks for testing to be performed in the production environment Receive questions regarding the budget from the project team Invalid project codes and cost centers How would you respond to a request from the project team for a number of dedicated onsite resources or only offshore testers? A project team requests for their own custom test deliverable templates rather than standard testing services templates Project team production deadlines are moved back two weeks, how would you handle that situation in order to complete the testing within the abbreviated time line You receive High Priority Ad hoc Requests (Red Teams) that begins immediately, how would you handle to assign resources to accommodate these service requests Customer does not provide any response to the estimate provided within the timeframe requested for a response. Customer requests a test start da

Data Migration Testing Approach 1. Objective 3 2. Introduction 3 3. Data Migration 3 4. Different types of Data Migration 3 4.1 Data Migration types 3 4.2 Road Map technologies 4 4.3 Data Volumes 4 5. Dependencies 4 5.1 Environmental Dependencies 4 5.2 Support Dependencies 5 5.3 Data Dependencies 5 6. SDLC Phases followed 6 6.1 Business Requirements Gathering 6 6.1.1 Risks in Data warehouse 6 6.2 Analysis & Design 6 6.2.1 Gap Analysis 7 6.2.2 Data mapping 7 6.2.3 Translation Tables 7 6.2.4 Specifications 7 6.2.5 Iterations 8 6.2.6 Data Cleanse 8 6.2.7 Cleansing Strategyneed to write an overview about this 8 6.3 Testing POC 8 6.3.1 Test Strategizing 9 6.3.2 Test Planning (Test approach) 9 6.3.3 Test Environment Setup 9 6.3.4 Test Execution 9 6.3.5 Result and Defect Analysis 9 6.3.6 Manual Testing Techniques 9 6.3.7 Reconciliation 13 6.3.8 File Integrities 13 6.3.9 Translation Table Validation 13 6.3.10 Design of A

The testing estimation process in place was quite simple. The inputs for the process, provided by the development team, were: the size of the development team and the number of working days needed for building a solution before starting systems tests. The testing estimation process said that the number of testing engineers would be half of the number of development engineers and one third of the number of development working days. A spreadsheet was created in order to find out the estimation and calculate the duration of tests and testing costs. They are based on the following formulas: Testing working days = (Development working days) / 3. Testing engineers = (Development engineers) / 2. Testing costs = Testing working days * Testing engineers * person daily costs. As the process was only playing with numbers, it was not necessary to register anywhere how the estimation was obtained. To exemplify how the process worked, if one development team said that to deliver a sol

J-Probe Memory debugger Memory Coverage Thread Analyser Profiler Memory Debugger Improve memory usage by finding objects Reducing excessive grabage collections Classes View(Data investigation) Profiler Ineffecient methods and it compares the snapshots to measure your perfromance metrics.

Terminal Emulation – QTP Automation Testing Topics to be covered 1. Basic understanding of the terminal emulator 2. Emulation terminology 3. Configuring the QTP to work with TE application 4. Automation testing methodology Basics of Emulator • Duplicates the functions of one system using a different system, so that second system behaves like a first system. • Computer simulation Example: AS400 and mainframes is a dark green color screen AS400 is introduced in the year of 1988 by IBM, formally renamed as IBM iseries but still called as AS400 is mid range server for the small business and large enterprises. It will work good within distributed network and web based applications for execution it uses OS400 ie operating systems. TN5250 Terminal emulation protocol IBM owned iseries access by TN5250 with WRQ’s reflection, humming bird’s host explorer, Cybele software’s Z scope Express 5250. AS400 is also a Mainframe which are used for large organizations, for critical applic

Objectives Test Management Tool – What, Why, Benefits etc To make participants aware of Test Process and controlling the process through security. Test Management Tool Test Management Overview What is Test Management Tool? Why Test Management Tool to be used? What are the benefits and false notion of using Test Management Tool? Various Test Management Tool tool in the market Introduction to QC QC course Content

The Priority will default to medium. Initiator should assign the priority based on the definitions in the table below. none low medium (default) high urgent immediate None

1. OVERVIEW 2. REPORTING A DEFECT 3. DEFECT PROCESSES                1.1 Defect Assignment                1.2 Daily Triage call                1.3 Daily Status Report                1.4 Developer Priorities for Fixing Defects                1.5 Vendor1 Developer                1.6 Vendor2 Team Ticket Updates 4. CLOSING A DEFECT 5. Defect EXAMPLES

QUALITY ATTRIBUTES To ensure a quality application, the test types that are defined in the test plan correspond to one or more Quality Attribute. Top Quality Attributes Portability – software transferred easily from one computer to the other Reliability – satisfy requirements without error, fault tolerance, recoverable Efficiency – time/resource - perform with minimum computer resources (memory, cycles) Human engineering – easily understood and used by human users Testability – easily verified by execution Understandability – read by software maintainer, operability Modifiability – easily revised by software maintainer Functionality Quality Assurance Software Quality Assurance involves the entire software development PROCESS – monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems found are dealt with. Quality Assurance is oriented to ‘prevention’. Quality Control Software Quality Control involves the tes

Acceptance Testing: Formal testing conducted to determine whether or not a system satisfies its acceptance criteria—enables an end user to determine whether or not to accept the system. Affinity Diagram: A group process that takes large amounts of language data, such as a list developed by brainstorming, and divides it into categories. Alpha Testing: Testing of a software product or system conducted at the developer’s site by the end user. Audit: An inspection/assessment activity that verifies compliance with plans, policies, and procedures, and ensures that resources are conserved. Audit is a staff function; it serves as the “eyes and ears” of management. Automated Testing: That part of software testing that is assisted with software tool(s) that does not require operator input, analysis, or evaluation. Beta Testing: Testing conducted at one or more end user sites by the end user of a delivered software product or system. Black-box Testing: Functional testing based on requi

Standards to be followed while creating test cases. 1. Test cases can be written in word document because it is easy to do spell check and check the syntax and semantics of the test steps. (It is not mandatory to use to word doc to develop manual test cases) 2. If you are writing the test cases in the excel sheet. a. Easy to upload the test cases into QC 9.0. b. Easy to update the test cases, test data and changes can be made in less time. c. Reduce the rework d. Utilize the features of excel in writing the test cases. e. Create/Execute test cases by using QTP tool. f. Easy to filter the pass/failed test cases to report g. Easy to insert/update/delete a test step row h. Easy to insert/update/delete a column 3. Each test case should have unique identified Test case number. 4. Each test case should include Scenario number, test case number and Test case name (S#_TC#_TestName) Test Scenario is closely mapped to a Business Scenario/Business Requirement. For example the di