About the Course
Manual testing is the process of manually testing a software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behaviour. Though it seems to be a simple process, there is a lot of indepth study required to perform manual testing on a software and get successful results.
A Manual Tester has to study every minute detail of a software very carefully. He needs to find out the expectations of a user from the software, understand the creation method of the software, plan his testing schedule, store and take down all the results from his tests, etc.
Topics CoveredTopics Covered
• Software Testing
• Goals of Testing
• Need of Testing Standards
• Testing Principles
• Testing Techniques
• When to Stop Testing
• Requirement Gathering
• Software Design
• Quality Assurance
• Quality Control
Life Cycle in Software Testing
• Software Development Life Cycle
• Software Testing Life Cycle
• Verification and Validation Model
Test Plan and Test Case
• Test Plan
• Test Cases
• Advantages of Test Cases
• Disadvantages of Test cases
Life Cycle Models
• Waterfall Model
• Linear Model
• Prototype Model
• Spiral Model
• Unit Testing
• White Box Testing
• Black Box Testing
• Integration Testing
• System Testing
• Acceptance Testing
• Alpha Testing
• Beta Testing
• Regression Testing
• Installation & Maintenance
Who should attendAny one who want to pursue career in Testing field.
Pre-requisitesA good testing program is a tool for both the agency and the integrator/supplier; it
Typically identifies the end of the “development” phase of the project, establishes the
Criteria for project acceptance, and establishes the start of the warranty period.
What you need to bringMaterials provided by us.
Key TakeawaysThere are two fundamental purposes of testing: verifying procurement specifications
and managing risk. First, testing is about verifying that what was specified is what was
delivered: it verifies that the product (system) meets the functional, performance,
design, and implementation requirements identified in the procurement specifications.
Second, testing is about managing risk for both the acquiring agency and the system’s
Vendor/developer/integrator. The testing program is used to identify when the work has
been “completed” so that the contract can be closed, the vendor paid, and the system
shifted by the agency into the warranty and maintenance phase of the project.