Manual Testing Course

Manual Testing Course

With a human interface, a software programme is tested manually by a quality assurance engineer in order to find defects. The responsibility of quality assurance engineers is to guarantee that any web or mobile application operates as efficiently as possible from the perspective of the end user. The behaviour of web or mobile applications is continuously examined, verified, and compared to the expected behaviour by QAs. Given that it considers the viewpoint of the end user, it is an essential component of any testing approach. A web page or mobile application’s rich user experience is what manual testing aims to ensure. Since the testing is done manually by skilled test engineers, automated test frameworks are not used in this testing. Among several advantages, the key advantage of manual testing is it assures that bug is found and debugged from the very first phases of online or application development.

marketing-product-manager-holding-marketing-promotion-plan monstertraining - Monster Trainings
ETL testing - Monster Trainings

WHY CHOOSE US

Monster Training offers manual testing to help you start your career as a Quality Assurance Engineer with a bang. In this course, students will be instructed by knowledgeable instructors from the field through live interactive classes and question-answer sessions. Clear your doubts at any time, anywhere through the 24/7 online portal for doing so. This course offers you recorded sessions to revise your curriculum at your pace and time. Assignments, real projects, and case studies will assist learners enjoy the learning process and lead to innovation. Additionally, it enhances the overall educational experience and strengthens your resume. You can monitor your performance and gauge your learning progress by completing weekly learning objectives with the aid of practice tests and assessments.

KEY FEATURES

100% Job Support
100% Practical Training
Live Project Experience

SEARCH ENGINE OPTIMIZATIONS CURRICULUM

  • 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
  • SDLC Models
  • Waterfall Model.
  • V Model
  • Rad model
  • Agile Model.
  • Prototype Model.
  • Spiral Model.
  • Static Testing
  • Dynamic Testing
  • White Box Testing
  • Black Box Testing
  • Gray Box Testing
  • Static Testing Techniques
  • Reviews
  • Walkthroughs
  • White Box Testing
  • Unit Testing
  • Integration Testing
  • Top-down Approach
  • Bottom up Approach
  • Hybrid Approach
  • Big bang Approach
  • Black Box Testing
  • System Testing
  • User Acceptance Testing (UAT)
  • Alpha Testing
  • Beta Testing
  • System Testing and Types of System Testing
  • Smoke / Sanity Testing
  • Formal Testing
  • Database Testing
  • Ad-hoc Testing
  • Re-Testing and Regression Testing
  • End-to-End Testing
  • Exploratory Testing
  • Buddy Testing
  • Pair Testing
  • Monkey Testing
  • UI Testing
  • Usability Testing
  • Intersystem Testing
  • Port Testing
  • Security Testing
  • Performance Testing
  • Load Testing
  • Stress Testing
  • Compatibility Testing
  • Installation Testing
  • Globalization Testing
  • Localization Testing
  • Recovery Testing
  •  
  • Testing Shows the Presence of Defects.
  • Early Testing.
  • Exhaustive Testing is Not Possible.
  • Testing is Context-Dependent.
  • 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.
  • Deliverables.
  • Test Analysis
  • Analyzing Functional Requirements
  • Preparing Requirement Clarification
  • Write Test cases
  • Review Test cases
  • Test Cases Template
  • Types of Test Cases
  • Difference between Test Scenarios and Test Cases.
  • Test Case Design Techniques
  • ECP
  • BVA
  • Decision Table Testing
  • State Transition Testing
  • Use case Testing
  • Preparing Test Data
  • Preparing RTM
  • Test Environment setup
  • Understand the SRS
  • Hardware and software requirements
  • Test Data
  • Write Test cases
  • Review Test cases
  • Test Cases Template
  • Types of Test Cases
  • Difference between Test Scenarios and Test Cases.
  • Test Case Design Techniques
  • ECP
  • BVA
  • Decision Table Testing
  • State Transition Testing
  • Use case Testing
  • Preparing Test Data
  • Preparing RTM
  • Test Environment setup
  • Understand the SRS
  • Hardware and software requirements
  • Test Data
  • What is Agile
  • What is Scrum/XP/Iterative Models
  • Sprint plan
  • Scrum Master
  • Stake Holder
  • Sprint Meeting
  • Scrum Call
  • Scrum Meeting
  • Backlogs
  • Advantages and Dis Advantages of Agile
  •  
  • QC/ALM
  • JIRA
  • Redmine
  • TestLink
  • BugTracker
×
×

Cart