Training Cost:
Rs 20,000 Non Refundable
Schedule of Classes:
2 Hrs on Week days(Mon-Fri), 6 Hrs Lab on Saturday
Certificates provided:
- 6 Mths Training + Project Certificate by Sebiz
- .Net Experience certificate by Sebiz
- 100% MCP Certificate assurance otherwise refund of Rs 6000
Sign Up for the Course Now
QC Industry Ready Program Syllabus
1. Fundamentals of testing (K2)
- 1.1 Why is testing necessary (K2
- 1.1.1 Software systems context (K1)
- 1.1.2 Causes of software defects (K2)
- 1.1.3 Role of testing in software development, maintenance and operations (K2)
- 1.1.4 Testing and quality (K2)
- 1.1.5 How much testing is enough? (K2)
- 1.2 What is testing? (K2)
- 1.3 General testing principles (K2)
- 1.4 Fundamental test process (K1
- 1.4.1 Test planning and control (K1)
- 1.4.2 Test analysis and design (K1)
- 1.4.3 Test implementation and execution (K1)
- 1.4.4 Evaluating exit criteria and reporting (K1)
- 1.4.5 Test closure activities (K1)
- 1.5 The psychology of testing (K2)
2. Testing throughout the software life cycle (K2)
- 2.1 Software development models (K2)
- 2.1.1 V-model (sequential development model) (K2)
- 2.1.2 Iterative-incremental development models (K2)
- 2.1.3 Testing within a life cycle model (K2)
- 2.2 Test levels (K2)
- 2.2.1 Component testing (K2)
- 2.2.2 Integration testing (K2)
- 2.2.3 System testing (K2)
- 2.2.4 Acceptance testing (K2)
- 2.3 Test types (K2)
- 2.3.1 Testing of function (functional testing) (K2)
- 2.3.2 Testing of non-functional software characteristics (non-functional testing) (K2)
- 2.3.3 Testing of software structure/architecture (structural testing) (K2)
- 2.3.4 Testing related to changes (confirmation testing (retesting) and regression testing) (K2)
- 2.4 Maintenance testing (K2)
3. Static techniques (K2)
- 3.1 Static techniques and the test process (K2)
- 3.2 Review process (K2)
- 3.2.1 Phases of a formal review (K1)
- 3.2.2 Roles and responsibilities (K1)
- 3.2.3 Types of review (K2)
- 3.2.4 Success factors for reviews (K2)
- 3.3 Static analysis by tools (K2)
4. Test design Techniques (K3)
- 4.1 The TEST DEVELOPMENT PROCESS (K2)
- 4.2 Categories of test design techniques (K2)
- 4.3 Specification-based or black-box techniques (K3)
- 4.3.1 Equivalence partitioning (K3
- 4.3.2 Boundary value analysis (K3)
- 4.3.3 Decision table testing (K3)
- 4.3.4 State transition testing (K3)
- 4.3.5 Use case testing (K2)
- 4.4 Structure-based or white-box techniques (K3)
- 4.4.1 Statement testing and coverage (K3)
- 4.4.2 Decision testing and coverage (K3)
- 4.4.3 Other structure-based techniques (K1)
- 4.5 Experience-based techniques (K2)
- 4.6 Choosing test techniques (K2)
5. Test management (K3)
- 5.1 Test organization (K2)
- 5.1.1 Test organization and independence (K2
- 5.1.2 Tasks of the test leader and tester (K1
- 5.2 Test planning and estimation (K2)
- 5.2.1 Test planning (K2)...
- 5.2.2 Test planning activities (K2)
- 5.2.3 Exit criteria (K2
- 5.2.4 Test estimation (K2)
- 5.2.5 Test approaches (test strategies) (K2)
- 5.3 Test progress monitoring and control (K2
- 5.3.1 Test progress monitoring (K1)
- 5.3.2 Test Reporting (K2)
- 5.3.3 Test control (K2)
- 5.4 Configuration management (K2)
- 5.5 Risk and testing (K2)
- 5.5.1 Project risks (K2)
- 5.5.2 Product risks (K2)
- 5.6 Incident management (K3)
6. Tool support for testing (K2)
- 6.1 Types of test tool (K2)
- 6.1.1 Test tool classification (K2)
- 6.1.2 Tool support for management of testing and tests (K1)
- 6.1.3 Tool support for static testing (K1)
- 6.1.4 Tool support for test specification (K1)
- 6.1.5 Tool support for test execution and logging (K1)
- 6.1.6 Tool support for performance and monitoring (K1)
- 6.1.7 Tool support for specific application areas (K1
- 6.1.8 Tool support using other tools (K1)
- 6.2 Effective use of tools: potential benefits and risks (K2
- 6.2.1 Potential benefits and risks of tool support for testing (for all tools) (K2)
- 6.2.2 Special considerations for some types of tool (K1
- 6.3 Introducing a tool into an organization (K1)