ISTQB+Manual Software Testing Training Course in Jaipur

Certification

Industry-oriented certification Digital Marketing training course to furnish your career to kick-start/grow at MNCs/Non-MNCs Organization & corporate

Experienced Faculty

Professional expert Sr. Digital Marketing Institute With 15+ Years of working experience will provide you industrial level training.

Placement Assistance

Receive placement assistance after completion of 70% training, E-Lite team will arrange interviews till you’ll get the placement.

LAB Facility

You can attain the practical training session to get the indutrial exposure & prepare for the corporate level challanges.

Workshop Sessions

You’ll attain knowledge on bases of real-time scenarios, live projects & best case study to complete E-Lite workshop.

Admin Support

E-Lite’s 7 days working admin team co-ordinates you for the fresh batch schedule/re-scheduling classes/arrange doubt classes.

ISTQB + Manual Software Testing Programme Details

Course Duration:30 – 35 HRS with Highly Skilled Corporate Trainers
ISTQB + Manual Software Testing Training for Modules – Weekdays / Weekend

E-Lite Institute Jaipur – ISTQB + Manual Software Testing Certification Training Delivery Method:

  • Web / Desktop Base.
  • Instructor-Led Classroom Sessions.
  • Presentations/Demonstration/Practicals of concepts.
  • Handouts/Assignments/Real-time Exposure to work on Clients.

ISTQB + Manual Software Testing Programme Modules

Manual + ISTQB Training CourseModules

<h3>Software Testing Overview</h3> <ul> <li>Introduction to Software Testing</li> <li>Objectives of Testing</li> <li>Software Development Process</li> <li>Project vs. Product</li> <li>Error / Fault / Failure</li> <li>Why Software has defects?</li> <li>Most common defects</li> <li>Cost of fixing defects</li> <li>Testing then &hellip; and Testing now&hellip;</li> <li>What is Verification &amp; Validation</li> <li>Difference between QA &amp; QC</li> <li>Role of a Tester</li> </ul> <h3><strong>Principles of Testing</strong></h3> <ul> <li>Early Testing</li> <li>Exhaustive Testing Impossible</li> <li>Defect Clustering</li> <li>Pesticide Paradox</li> <li>Testing is Context Dependant</li> <li>Testing Should Show Presence of Defects</li> <li>Absence of Error is a Fallacy</li> </ul> <h3>Software Development Life Cycle (SDLC)</h3> <ul> <li>SDLC Phases</li> <li>SDLC Models&nbsp; <ul> <li>Waterfall Model</li> <li>V Model</li> <li>RAD Model</li> <li>Prototype Model</li> <li>Spiral Model</li> <li>Agile Model</li> </ul> </li> </ul> <h3>Software Testing Methodologies</h3> <ul> <li>Static Testing</li> <li>White Box Testing</li> <li>Black Box Testing</li> <li>Gray Box Testing</li> </ul> <h3>Static Testing Techniques</h3> <ul> <li>Reviews</li> <li>Walkthroughs</li> </ul> <h3>White Box Testing</h3> <ul> <li>Unit Testing</li> <li>Integration Testing</li> </ul> <h3>Black Box Testing</h3> <ul> <li>System Testing</li> <li>User Acceptance Testing (UAT)&nbsp; <ul> <li>Alpha Testing</li> <li>Beta Testing</li> </ul> </li> </ul> <h3>System Testing and Types of System Testing</h3> <ul> <li>Smoke / Sanity Testing</li> <li>Formal Testing</li> <li>Priority Based/Risk Based Testing</li> <li>Ad-hoc Testing</li> <li>Re-Testing and Regression Testing</li> <li>End-to-End Testing</li> <li>Exploratory Testing</li> <li>Benchmark Testing</li> <li>Monkey Testing</li> <li>UI Testing</li> <li>Usability Testing</li> <li>Security Testing</li> <li>Performance Testing</li> <li>Load Testing</li> <li>Stress Testing</li> <li>Compatibility Testing</li> <li>Installation Testing</li> <li>Globalization Testing</li> <li>Localization Testing</li> <li>Recovery Testing</li> </ul> <h3>Software Testing Life Cycle (STLC)</h3> <ul> <li>Test Planning&nbsp; <ul> <li>Test Strategy</li> <li>Test Plan</li> </ul> </li> <li>Test Analysis&nbsp; <ul> <li>Analyzing Functional Requirements</li> <li>Preparing Requirement Clarification</li> </ul> </li> <li>Test Preparation&nbsp; <ul> <li>Identifying &amp; documenting Test Scenarios</li> <li>Test Case Design Techniques&nbsp; <ul> <li>ECP</li> <li>BVA</li> <li>Decision Table Testing</li> <li>State Transition Testing</li> <li>Use case Testing</li> </ul> </li> <li>Preparing Test Cases</li> <li>Preparing Test Data</li> <li>Preparing RTM</li> </ul> </li> <li>Test Execution&nbsp; <ul> <li>Build Release Process</li> <li>Executing Testcases</li> </ul> </li> <li>Defect / Bug Life Cycle</li> <li>Defect Management&nbsp; <ul> <li>What is defect?</li> <li>Defect Classification</li> <li>Defect Severity &amp; Defect Priority</li> <li>Defect Report Template</li> <li>Defect Reporting &amp; Defect Tracking</li> </ul> </li> <li>Test Closure&nbsp; <ul> <li>Criteria for Test Closure</li> <li>Status Reports (Daily and Weekly)</li> <li>Test Summary Reports</li> <li>Agile Testing</li> <li>Database Testing</li> </ul> </li> </ul> <h3>Test Management &amp; Defect Management Tools</h3> <ul> <li>ALM (Quality Center)</li> <li>Jira</li> </ul> <h3>Structured Query Language</h3> <ul> <li>Introduction to SQL</li> <li>Joining Tables</li> <li>Deleting Data</li> <li>Using Views</li> <li>Deleting Data</li> <li>Grouping Data</li> <li>Between Operator</li> </ul> <h3>Unix Basic Command</h3> <ul> <li>Grep Command</li> <li>Find Command</li> <li>SSH Command</li> <li>VIM Command</li> <li>LS Command</li> <li>PWD Command</li> <li>CD Command</li> <li>Shut Down Command</li> <li>FTP Command</li> <li>Service Command</li> <li>PS Command</li> <li>Kill Command</li> <li>RM Command</li> <li>CP Command</li> <li>MV Command</li> <li>CAT Command</li> <li>PASSWD Command</li> <li>MKDIR Command</li> <li>UNAME Command</li> <li>WHATIS Command</li> <li>TAIL Command</li> <li>LESS Command</li> <li>PING Command</li> <li>Date Command</li> </ul>
<h3>Fundamentals of Testing</h3> <ul> <li>Why is testing necessary</li> <li>Software systems context</li> <li>Causes of software defects</li> <li>Role of testing in software development, maintenance and operations</li> <li>Testing and quality</li> <li>How much testing is enough</li> <li>What is testing</li> <li>Seven testing principles</li> <li>Fundamental Test Process</li> <li>Test Planning and control</li> <li>Test analysis and design</li> <li>Test implementation and execution</li> <li>Evaluating exit criteria and reporting</li> <li>Test closure activities</li> <li>The psychology of testing</li> <li>Code of ethics</li> </ul> <h3>Testing throughout the Software Life Cycle</h3> <ul> <li>Software Development Models</li> <li>V model</li> <li>Iterative models</li> <li>Testing within a lifecycle model</li> <li>Test Levels</li> <li>Component testing</li> <li>Integration testing</li> <li>System testing</li> <li>Acceptance testing</li> <li>Test Types</li> <li>Functional testing</li> <li>Non-functional testing</li> <li>Structural testing</li> <li>Regression testing</li> </ul> <h3>Static Techniques</h3> <ul> <li>Static techniques and the test process</li> <li>Review Process</li> <li>Activities of a formal review</li> <li>Roles and responsibilities</li> <li>Types of reviews</li> <li>Success factors for reviews</li> <li>Static analysis by tools</li> </ul> <h3>Test Design Techniques</h3> <ul> <li>Test development process</li> <li>Categories of test design techniques</li> <li>Black box techniques</li> <li>Equivalence Partitioning</li> <li>Boundary Value Analysis</li> <li>Decision Table Testing</li> <li>State Transition Testing</li> <li>Use case testing</li> <li>White box techniques</li> <li>Statement testing and coverage</li> <li>Decision testing and coverage</li> <li>Other structure-based techniques</li> <li>Experience-based techniques</li> <li>Choosing test techniques</li> </ul> <h3>Test Management</h3> <ul> <li>Test Organization</li> <li>Test organization and independence</li> <li>Tasks of test leader and tester</li> <li>Test Planning and Estimation</li> <li>Test planning</li> <li>Test planning activities</li> <li>Entry criteria</li> <li>Exit criteria</li> <li>Test estimation</li> <li>Test strategy, test approach</li> <li>Test Progress Monitoring and Control</li> <li>Test progress monitoring</li> <li>Test reporting</li> <li>Test control</li> <li>Configuration Management</li> <li>Risk and Testing</li> <li>Project risks</li> <li>Product risks</li> <li>Incident Management</li> </ul> <h3>Tool Support for Testing</h3> <ul> <li>Types of Test Tools</li> <li>Tool support for testing</li> <li>Test tool classification</li> <li>Tool Support for management of testing and tests</li> <li>Tool support for static testing</li> <li>Tool support for test specification</li> <li>Tool support for test execution and logging</li> <li>Tool support for performance and monitoring</li> <li>Tool support for specific testing needs</li> <li>Effective Use of Tools</li> <li>Potential benefits and risks</li> <li>Special considerations</li> <li>Introducing a tool into an organization</li> </ul> <h3>Certification Advantages</h3> <ul> <li>Gain recognition for testing as an essential and professional software engineering specialization by industry</li> <li>Obtain a standard framework for the development of testers&rsquo; careers</li> <li>Become professionally qualified testers to be recognized by employers, customers and peers, and raise the profile of testers</li> <li>Promote consistent and good testing practice within all software engineering disciplines</li> <li>Help in identification of testing topics that are relevant and of value to industry</li> <li>To increase chances of software suppliers to hire and thereby gain commercial advantage over their competitors by advertising their tester recruitment policy</li> <li>Add an opportunity for testers or those with an interest in testing to acquire an industry recognized qualification in the subject</li> </ul>

Find the course details below.

Duration of Module

ISTQB + Manual Course Module Course Duration
ISTQB + Manual Software Testing 30 – 35 (Hours)

Batch Timings

ISTQB + Manual Course Schedule Course Timing
Monday to Friday 8:00 AM – 10:00 AM
Monday to Friday 10:00 AM – 12:00 PM
Monday to Friday 2:00 PM – 4:00 PM
Monday to Friday 4:00 PM – 6:00 PM
Saturday/Sunday 8:00 | 12:00 | 2:00 | 4:00
Sunday 8:00 AM – 10:00 AM
Sunday 10:00 AM – 12:00 PM
Sunday 2:00 PM – 4:00 PM
Sunday 4:00 PM – 6:00 PM