Our manual software testing course includes basic to advanced level and our manual testing course is designed to get the placement assistance. Our manual testing trainers are manual software testing certified experts and experienced working professionals with hands on real time multiple Manual Testing projects knowledge. We have designed our manual testing course content and syllabus based on students requirement to achieve everyone's career goal.
Live Technoworld Our manual software testing training centers are equipped with lab facilities and excellent infrastructure. Manual testing training in gurgaon conducted on day time classes, weekend training classes, evening batch classes and fast track training classes.
1. Manual Testing Syllabus
INTRODUCTION TO SOFTWARE TESTING
What is Testing
What is Quality
2. SOFTWARE DEVELOPMENT LIFE CYCLE
Initial Requirement phase
3. ADVANTAGES OF WATERFALL MODEL:
Easy to understand ,easy to use
Provides structure to the in experienced stuff
Milestones are well understand
Sets requirement stability
Good for management control(plan, stuff, track)
Works when quality is more important than cost or schedule.
4. DIS ADVANTAGE:
All requirement must be known upfront
Deliverables are create for each phase are considered frozen.(In simple words every output must be finalized in this model)
Can give a false impression of progress
Does not reflect problems solving nature of software development iteration phases
Integration is one of the big bang at the end
Little opportunity for customer to preview the system (until it may be too late).
5. WHEN TO USE THE WATERFALL MODEL:
Requirement are very well known
Product definition is stable
Technology is understand
New versions from the existing version
Porting an existing product to a new platform.
6. ADVANTAGES OF V MODEL:
It emphasize both verification and validation for the entire development
Every deliverable must be tested
Project manager track progress by milestone
Easy to use
7. DIS ADVANTAGES:
Does not handle parallel events in some times
Can ‗t allow dynamic requirements
Can‘t estimate risk analysis
8. WHEN WE CAN GO FOR V MODEL:
When time is high reliability of the application (ex: hospital manager application)
All requirement must be known upfront application
Technology is understand
9. INCREMENTAL MODELS:
These models are best suitable for the big application development purpose.
No need to known all requirements before developing
Requirement may not be stable
Proto type model(rapid application development)
Company people develop a proto type during requirement phase
Proto type be evaluated by a user
User gives corrective feedbacks
Developers define the prototype code
When the user is satisfied the corresponding requirement will become base for original application.
11. INTERNAL PROCESS
A preliminary proper model developed.
The model is the partial requirement specification for the prototype
Designers build Database, UIT, Algorithms
Designers demonstrate the project to the customer for getting requirement suggestion and early feedback
This loop will continue until the user is satisfied
12. ADVANTAGES OF PROTOTYPE MODEL:
Customer can see the system requirement as they are being gathered function requirement
Developer learns from the customer
A more accurate of end product
Unexpected requirement are accommodate(dynamic)
Annoys flexibility designing and development awareness of additional needs functionality
Bad reputation from the customer for quick and dirty methods
Over all maintains may be overload.
The customer may want the prototype developed
Process may continue for ever
14. WHEN WE CAN GO FOR PROTO TYPE MODEL:
Customer is not sure with his requirement
When the application is object oriented.
1) Requirement planning phases:
A work is utilizing structure to discuss of business problems PROCESS:
1) In this customer And customer representation people and company business
analysis and subject matter export, project manager, team manager will
2) USER DESCRIPATION PHASE:
By the time of gathering requirement some company employees has to work
at customer side and they will gathering the requirement from the customer.
All requirement are be stored in a modularized tool this tool are capturing
requirement as well as generate screens (GUI)
What are the information gathering by the tool the information will sent to
the company for a particular period time
3) Contraction phase:
What are information is gathering from the tools development are going to
generate the code
4) Customer over phase:
Application will be deployed in customer environment
training will be provided by the test engineers to customer or customer
Acceptance testing will be carried out in this phase only.
16. ADVANTAGES OF RAT MODEL:
Reduce the cycle time
Entire work must be time box
Customer involves throughout life cycle
Excel rated process can gives false impression
Risks are never achieving closer
Hard to use with legacy system.
We need to have a modularized tool to implement this process
Developers and customer must be committed with rapid the activists
18. WHEN WE CEN GO FOR RAT MODEL:
If we know basic requirements.
Whenever client want to see all SDLC activists.
Application must be time boxed
Whenever functionality is need.
High performance is not required for rat model
Load technical risk is enough
This model is 4GL to rat prototyping into waterfall model
Each cycle involving same sequence of the steps are the waterfall model
20. OBEJECTIVIES OF SPRIAL MODEL:
2)s/w and h/w application
3)critical success factor areas
Identify designing in technical document
Identify all independent areas prepare for the script for independent paths (systematic complexity)
21. Control structural testing:
In this developers are going to check the completeness and correctness of the program by implementing loops and conditions.
22. Programming technique testing:
In this developers are going to monitor execution time
If the code is not executed according to developers.
23. Mutation testing:
By the time of changing program whether their change is impacting on unchanged areas then that technique is called mutation testing.
24. Integration testing:
After completion of unit testing developers are going to considering on integration areas.
In integration testing developers are going to establish the relation between related units.
By the time of conducting integration testing developers are going to follow approach