Testing Syallabus
Testing Syallabus
1. Qtp Script 1. Tiers 2. Qtp script basics 3. Qtpscript code generation methodologies 2. Qtp for web testing 1. 2. 3. 4. 5. 6. 7. 8. 3. Qtpscript language objects Password encryption Indexing concept Ordinal identifiers Handling popup Analog recording working with other add-ins Case study Vb script
1. Basics 2. Variables 3. Reservations 4. Operators 5. Conditions 6. Loops 7. Arrays 8. Functions in VB script, User defined functions, Examples 9. Components in Vbscript A). Keyboard automation, B). Excel, C). Notepad, D). word, E). Working with Regular Expression F). Msoutlook G). Working with database. 4. Qtp Script for Windows based Software testing A). Working with Java-add in B). Working with .net-add in C). Working with SAP- Add in D). Working with SIEBEL Add in E). Working with People soft Add-in F). Working with Standard window addin 5. 6. 7. Qtpscript for CLI (Command line interface) based software Qtpscript for Web service testing: Qtpscript for Mobile testing:
8.
9.
Software Test Automation Framework or Automation life cycle A. Sign-in B. Study SRS C. Folder structure creation D. Create repository E. Create library F. Write Test script G. Adding Recoveries H. Adding utilities 1. Reporter object 2. Environment object 3. Data table object 4. Description object 5. Synchronization point I. Batch testing or drivers 1. Test Batch runner 2. Automation object model
Manual Testing:
1.SDLC
1. S/w Testing principles: 2. Software product vs Software project: 3. Software development life cycle: Water fall model Prototype model Incremental model Spiral model RAD model
2. Testing Stages:
1. Document Testing BRS SRS HLD,LLD
2. Unit Testing Basic Path Coverage Control structure coverage Program technique coverage
Mutation coverage
3. Integration testing Top down approach Bottom up approach Hybrid approach System approach
4. Software Testing Functional testing A). Behavioral testing B). Input domain testing C). Error handling testing D). Manipulation testing E). Database testing F). Data volume testing G). Inter system testing
A). Usability testing B). Compatibility testing C). Hardware configuration testing D). Performance testing E). Security testing F). Multi languity testing
3. STLC
SDLC Vs STLC STLC 1. 2. 3. 4. 5. 6. Test initiation: Test planning: Test design Test execution Test reports Test closure
Scope & Objective Business issues Test responsibility matrix Roles & Responsibilities Communication & Status reporting Test Automation & testing tools Defect reporting & tracking Configuration management Test measurement & metrics Risks & Assumptions Training need
1.Test initiation:
A). Testing Team Formation B). Identity tactical risks Lack of skills to select a tester Lack of time to select a tester Lack of resources Lack of documentation Delays in deliveries Lack of development team seriousness Lack of communication C). Prepare test plan What to test? How to test? Who to test? When to test? What to test? 1. Test plan Id 2. Introduction 3. Features or Requirement 4. Features to be tested 5. Features not to be tested How to test? 6. Test strategy 7. Test environment 8. Test deliverables 9. Entry criteria 10. Suspension criteria 11. Exit criteria Who to test? 12. Staff & training need 13. Responsibilities When to test? 14. Schedules 15. Risks & Assumption 16. Approvals D).Review Test plan
B). Test Scenarios & Test cases 1. Functional spec based Test design 2. Use case based 3. Screen based 4. Non-Functional spec Techniques 1. Boundary value analysis 2. Equivalence portioning 3. Decision table 4. Orthogonal array 5. State transition flow 6. Error guessing 7. portability 8. Usability 9. Hardware configuration 1. Client server architecture 2. Sql Management studio 3. Types of sql commands DDL DML TCL DDL 4. Joins 5. Sub query 6. Functions
C).
Sql Commands
D). Test Data E). Review Testing Documents 4. Software Test Execution:
A). Formal meeting B). Define test execution levels C). Establishing environment D). Smoke Testing E). Real testing F). Defect tracking G). Defect tracking process H). Test case related defect fixing
I). Test data related defect fising J). Test environment related K). Code related or bug fixing L). Bug life cycle M). Test cycle
6. Acceptance 7. Sign-off
V (Double V model)
1. Verification
2. Validation 3. Automation
Load Runner:
1. 2. 3. Vugen Controller Result Analysis
Quality center:
1. Why we need Quality center 2. Quality center tool Architecture I. A). Network Admin Responsibilities B). Creating database for new project or product
II.
Test lead responsibilities A). Selecting employees B). Assign responsibilities to different roles C). Allocating modules for testers D). Software testing topics selection E). Design test execution levels
III.
IV. V.