Software Testing (Manual) Online Live Class by Experts
Our Training/Internship Process
Software Testing (Manual) - Syllabus, Fees & Duration
Manual Testing Syllabus
- What is Software testing?
- Importance of Software testing
- Basic terminology of Software testing
- Difference between Manual and Automated Testing
- Software testingPrinciples
- Levels of Testing
- Software development life cycle
- Requirements phase
- Analysis phase
- Design phase
- Coding phase
- Testing phase
- Release and maintenance phase
- Software Development life cycle models
- Waterfall model
- Agile model
- Spiral model
- V model
- Software Testing Life Cycle
- Testing Constraints
- Static Test Design
- Formal review
- Informal reviews
- Walkthroughs
- Technical review
- Inspection
- Dynamic test design
- White-box testing
- White-box testing technique
- Black box testing
- Black box testing technique
- Grey box testing
- Test plan document
- Scope of document
- Objective of testing
- Customisation of Test Plan document
- Requirement Traceability Matrix
- Importance of Test case
- Test case template
- Test Scenario
- Test Strategy
- Functional Testing Types
- Sanity Testing
- Smoke Testing
- Retesting
- Regression testing
- Adhoc testing and types
- UI testing
- Positive Testing
- Negative Testing
- Alpha and Beta Testing
- Non-functional Testing
- Performance testing
- Load testing
- Stress Testing
- Volume Testing
- Security testing
- Portability testing
- What is a bug?
- Bug life cycle
- Severity
- Priority
- Types of Bugs
- Bug Report Template
- Metric types and calculation
- Test Report Template
MODULE 1 - Introduction to Manual Testing
MODULE 2 – SDLC and STLC
MODULE 3 – Static and Dynamic Testing
MODULE 4 – Test Plan and Test Case Documents
MODULE 5 – Types of Testing
MODULE 6 – Bug Report and Test Report Documents
This syllabus is not final and can be customized as per needs/updates
- Since 2001, Making IT Experts by Experts
- Duration: 30 Hours (Vary as per your skill)
- Course Fees
- Individual Live Classes (1:1)
- Batch Classes @ Low Fees
- Training on Your Time, Any Where
- Access to Recorded Videos
- Practical Internship on Projects
- 100% Placement Support by our jobsNEAR.in
- Training/Internship Certificate
- Agra
- Ahmedabad
- Alappuzha
- Aurangabad
- Bangalore
- Belgaum
- Bellary
- Bhubaneswar
- Chennai
- Cochin
- Coimbatore
- Delhi
- Dindigul
- Erode
- Gulbarga
- Guntur
- Gurgaon
- Haryana
- Hyderabad
- Idukki
- Indianpolis
- Indore
- Jaipur
- Kalyan
- Kannur
- Kanpur
- Kasaragod
- Kerala
- Kolkata
- Kollam
- Kottayam
- Kozhikode
- Lucknow
- Madurai
- Malappuram
- Mangaluru
- Mumbai
- Mysuru
- Nagpur
- Nashik
- Navi Mumbai
- Nizamabad
- Noida
- Palakkad
- Pathanamthitta
- Pune
- Punjab
- Salem
- Shimla
- Solapur
- Surat
- Thane
- Thanjavur
- Thirunelveli
- Thoothukudi
- Thrissur
- Tiruchirappalli
- Tiruppur
- Trivandrum
- Vadodara
- Varanasi
- Vellore
- Vijayawada
- Visakhapatnam
- Wayanad
Course Highlights
Our Locations
Manual software testing takes longer and requires more effort, but it is necessary to see if automation is viable. With live projects, the course covers manual testing from the basics to the advanced level. Manual testing consumes a considerable amount of human resources, is expensive in the near term, and takes a long time. The goal of the course is not to teach the fundamentals of testing, but to take it to the next level. The course covers software testing, the software life cycle, the waterfall model, software test design approaches, software testing methodology, testing levels, QA, and QC testing, among other topics. Before any creative application can be automated, it must first be manually tested. As a capable manual tester, you may be able to receive a good living. And it isn't going out of vogue anytime soon because every software application, regardless of the technology used to develop it, needs to be tested. It's a time-consuming process that requires the tester to be alert, resourceful, skilled, opinionated, speculative, and innovative, among other attributes. Manual testing permits human observation, which may be more real for noticing potential flaws in dynamically accusing GUI designs and usability testing. 
