Manual Testing

Ensure flawless software with hands-on testing.

Ensure software quality with systematic test planning, execution, and defect tracking. Manual testing validates applications from an end-user perspective to deliver bug-free products.

OnlineITvidhya’s Manual Testing course is a combination of Code Review, Integration Testing, Non-Functional Testing, Defect Management, and many more, the course provides functional knowledge.

Why Choose Us?
OnlineITvidhya Manual Testing Online Training with Live Projects. Real-Time experts with more than 10+ years of work experience in the industry provide the training. By discussing all relevant data, our instructors promise to keep you ahead of any other person in the field. Training will start with the fundamentals and cover tools for bug tracking and test management (ALM, Jira, Test Link, Bugzilla, Redmine).

What after Course?
Once you have finished the Manual Testing course, you will be able to:
Know the underlying ideas behind software testing, such as its goals, procedures, standards, and techniques.
Recognize manual testing procedures such as regression, system, integration, and unit testing as well as software testing procedures.
Discover how to organize a testing project, create test cases and data, carry out testing activities, handle faults, and produce a test report.
Learn how to communicate with engineers and develop various types of software testing documentation.
For a testing project, create and carry out software testing activities.
Use effective communication to engage with and work with stakeholders.
All of the topics needed to pass the Manual Testing certification exam are covered in our manual testing course. The instructor will distribute the manual testing certification manual, example questions for the manual testing certification, and practice questions for the manual testing certification.

Who can learn this course?
Anyone who wishes to begin a career in the IT industry can choose the manual testing course. Software testing doesn’t require any formal education. The main criterion for testing is a basic understanding of code.

What are the prerequisites of OnlineITvidhya’s Manual Testing online Training program?
Any technical degree or its equivalents, such as a B.Tech, M.Tech, engineering degree, bachelor’s or master’s in computer science, and familiarity with fundamental programming languages.

Placement Assistance:
Students who have finished courses with OnlineITvidhya will receive aid with placement. Our instructors will help you practice the course according to the schedule, by assigning daily tasks for completion. Our team will conduct mock interviews, to ensure that you are set to advance your career.

Course Curriculum

Module 1: Software Testing Introduction
  • Introduction to Software Testing
  • Objectives of Testing
  • Project vs. Product
  • Error / Fault / Failure
  • Why Software has defects?
  • Importance of testing
  • Roles and Responsibilities
  • What is Quality?
  • How much testing is enough?
  • Differences between Manual and Automation Testing.
  • Most common defects
  • Cost of fixing defects
  • Testing then … and Testing now…
  • SDLC Phases
    • Requirements Phase
    • Analysis Phase
    • Design phase
    • Coding Phase
    • Testing phase
    • Delivery and Maintenance Phase
  • What is Verification & Validation
  • Difference between QA & QC
  • Role of a Tester
  • Waterfall Model
  • V Model
  • Rad model
  • Prototype Model
  • Spiral Model
  • Agile Model
  • Waterfall Model
  • V Model
  • Rad model
  • Prototype Model
  • Spiral Model
  • Agile Model
  • Testing Shows the Presence of Defects.
  • Early Testing.
  • Test execution levels
  • Exhaustive Testing is Not Possible.
  • Testing is Context-Dependent.
  • Defect Clustering.
  • Pesticide Paradox.
  • Absence of Error.
  • Test Planning
    • Test Strategy
    • Test Plan
  • Test Plan Document
    • Object
    • Scope of Testing
    • Schedule
    • Approach
    • Roles & Responsibilities
    • Assumptions
    • Risks & Mitigations
    • Entry & Exit Criteria
    • Test Automation
  • Test Analysis
    • Analyzing Functional Requirements
    • Preparing Requirement Clarification
  • Test Cases Template
  • Types of Test Cases
  • Difference between Test Scenarios and Test Cases
  • Write Test cases
  • Review Test cases
  • Preparing Test Data
  • Preparing RTM Test Case Design Techniques
    • BVA (Boundary Value Analysis)
    • ECP (Equivalence Class Partition)
    • Decision Table Testing
    • State Transition Testing
    • Use case Testing
  • Test Environment setup
    • Understand the SRS
    • Hardware and software requirements
    • Test Data
  • Execute test cases
  • Formal Meeting
  • Configuration Management Repository
  • Creating Test Batches
  • Defining Test Sets
  • Adding Tests to a Test Set
  • Scheduling Test Runs
  • Running Tests Manually
    • Viewing and Analyzing Test Results
  • What is defect?
  • Types of Bugs
  • Bug/Defect Lifecycle
  • Defect Classification
  • Defect Severity & Defect Priority
  • Defect Report Template
  • Defect Reporting & Defect Tracking
  • Criteria for Test Closure
  • Status Reports (Daily and Weekly)
  • Test Summary Reports
  • ISO Software Testing Standards
  • IEEE Standard for Software Test Documentation
  • ANSI Standards for Software Testing
  • Introduction to Database Testing
  • Layers of application
  • Why testing at data layers is important?
  • Primary functions of a database layer
  • Why to test and what to test in a database?
  • Differences between UI Testing and Database testing
  • Skills needed to perform database testing
  • How to test a database
  • Types of SQL Statements:
    • DQL – Data Query Language
    • DML – Data Manipulation Language
    • DDL – Data Definition Language
    • DCL – Data Control Language
    • TCL – Transaction Control Language
    • DRL – Data Retrieval Language
  • Module 14: Agile & Scrum

    • Agile & Scrum
      • What is Agile Testing
      • Getting Agile with Scrum
      • Characteristics of Scrum
      • Scrum Approach
      • Agile testing quadrants
      • Agile Testing Principles
      • Exploratory Testing
      • User Stories
      • Story points
      • Designing test scenarios and test cases based on user stories
    • Agile Methodology
      • Why Agile is so popular?
      • When to go for Agile?
      • For what kind of projects Agile is suitable?
      • For what kind of projects Agile is not suitable?
      • Comparison of traditional models with Agile
      • Compare Agile with waterfall model
      • Compare Agile with V Model
      • Benefits of Agile Methodology
      • Drawbacks of Agile Methodology
      • Agile Methodology Frameworks
      • Introduction to Scrum
      • What is Scrum?
      • What kind of projects scrum is suitable?
      • For what kind of projects scrum is not suitable?
      • A Discussion on Sprint Planning
      • Discussion on Story Cards
      • Scrum Roles
      • Scrum Artifacts
      • Scrum Events

JIRA Introduction

  • How to install JIRA
  • JIRA Features
  • Creating a scrum project in JIRA
  • Adding users to our JIRA Account
  • JIRA Issue types
  • Workflow for a project
  • Creating product backlog in JIRA
  • Creating Epics in JIRA
  • Creating user Stories in JIRA
  • Writing Test cases in JIRA
  • Executing Test cases from JIRA
  • Adding Bugs to the JIRA project
  • Attaching screenshots of defects in JIRA
  • Adding Users to our JIRA Account
  • Importance of Defect Life Cycle and understanding the various stages/states of a defect.
  • Converting a Defect Life Cycle into JIRA workflow for a project
  • Assigning, Closing, Adding comments, etc… to the JIRA bugs.
  • Creating and Customizing JIRA Dashboard.
  • Introduction to Test Link
  • Benefits of Test Link
  • Test Link Installation
  • Creating Test Project
  • Creating Test Plan
  • Build Creation
  • Creating Test Suite
  • Creating a Test Case
  • Assigning Test Cases to Test Plan
  • How to Prepare Effective Resume
  • How to Explain Live Project in Interview
  • FAQS
  • 1 to 1 Mock Interviews
  • Job Assistance

[upcomingbatcheslist]

Lifetime Access

You will be provided with lifetime access to presentations, quizzes, installation guides and notes.

Assessments

After each training module there will be a quiz to assess your learning

24*7 Support

We have a lifetime 24*7 Online Expert Support to resolve all your Technical queries.

Forum

We have a community forum for our learners that facilitates further learning through peer interaction and knowledge sharing.

Certificate

After successfully complete your course OnlineITvidhya will give you course completion Certificate.

Mock Interviews

Explore what the real-time interviews expect from you.

OnlineITvidhya is a very good platform for beginners. The great Training institute for Manual Testing.

Haripriya

OnlineITvidhya is really very good for online learning. I have attended manual testing course which are really well taught.

Prathap

OnlineITvidhya is a good platform to learn. Overall course was great and informative. Very good trainer, explained all concepts well and clearly.

Shalini

FAQs

What is Manual Testing?
  • Manual testing is the process of manually executing test cases without using any automation tools to identify defects in a software application.
  • Manual testing can be categorized into: 1. Functional Testing 2. Non-Functional Testing 3. Regression Testing 4. Integration Testing 5. System Testing

Manual Testing: Testers execute test cases manually. Automated Testing: Test scripts are executed using tools like Selenium, QTP, etc.

A test case is a set of conditions, inputs, and expected results used to verify that a software application works as intended.

A test plan is a document that outlines the testing strategy, objectives, resources, schedule, and scope of testing for a project.

Severity: The impact of a defect on the system. Priority: The urgency of fixing the defect.

Regression testing is performed to ensure that recent code changes do not negatively affect existing functionalities of the application.

Smoke testing is a preliminary test to check whether the basic functionalities of an application are working properly before detailed testing.

Verification: Ensures the product is built correctly according to specifications. Validation: Ensures the built product meets user requirements.

Exploratory testing is an informal testing approach where testers explore the application, learn about its functionalities, and design test cases on the fly.