ISTQB Software Testing Process
As part of our Manual Testing Training, you will comprehensively learn the fundamentals of software testing. We will assume that you do not have any IT or Software Testing knowledge and walk you through with all the basics required to effectively get started with the Manual Testing Projects. We will make sure you have gained confidence from the session-1 well beyond familiarisation - before moving onto pursuing testing projects from session-2.
Following topics are covered in the first Live Manual Testing session: Software Testing Process
- Introduction to IT: Software Development Process, Cross-functional groups, Development Work products
- Software Development Process Models (SDLC)
- V-Model and W-Model – with numerous Software Testing Project examples
- Software Test Engineering
- Software Testing Fundamentals
- ISTQB Software Testing Process / Testing Life cycle (STLC)
- Objectives of Software Testing
- Levels of Testing
- Types of Testing
- Static & Dynamic Testing
- Functional Testing, Non-Functional Testing, Regression Testing
- Testing Levels – Testing Types correlation
- Test Level Pyramid (System Integration Testing, End to End Testing)
- Integrating STLC into SDLC
- ISTQB Testing Principles (Practical application of Testing principles in various Testing phases in the subsequent sessions)
Watch this FREE video that covers Software Testing Process which is the first session from our 3-months project based Manual Testing Training . This should indeed give you an idea of what’s coming up mainly focusing on all the Testing tasks aligning to ISTQB Testing process.
This session covers the following topics:
- Insight into IT & Software Testing
- Development Process – SDLC and Process Models
- ISTQB Testing Process – STLC
- Testing Objectives, Testing Levels and Testing Types
- Test Level Pyramid (SIT and E2E)
- Integrating STLC into SDLC
- ISTQB Testing Principles
Fundamental Testing Process
We will go beyond the Software Testing fundamentals mainly focusing the Software Testing Process and integration with the development life cycle to keep the session realistic albeit it’s a theory based session with the intent of giving you an exposure to the industry best practices through numerous testing project examples. Few advanced testing concepts are touched upon too, for example SIT & End-to-End testing levels that are not covered in conventional theory based training or in the ISTQB foundations syllabus.
We shall learn and master V model and W model throughout the Manual Testing Course whilst also learning as how to integrate Software Testing life cycle into the development life cycle.
We have dedicated Manual Testing sessions to cover all the Software Testing phases in the Fundamental Testing Process:Test Planning, Test Analysis and Test Design, Test Implementation, Test Execution, Test Reporting and Test Closure.
Every IT organisation either practices V / W model or an Agile Methodology.
Predominantly development processes used can be more generally connected by the V-model where the “V” in linear sequential fashion describes the graphical arrangement of the development phases whilst emphasising on various Testing levels. “V” is synonymous for V & V (Verification and Validation).
V model is very simple and easy to understand. By the ordering of activities in time sequence, the connection between development and Testing activities becomes quite clear. Oppositely laying activities complement one another serves as a basis for Testing tasks. For instance, the System Testing Level is carried out on the basis of the Specification phase. V model gives the impression that the test activities start after the implementation which is the drawback of V model. However, in the description of the individual activities the preparatory work is typically listed. Other drawback of V model: Bug life cycle is missing in order to demonstrate planned-in removal of defects. This is overcome in W Model.
In order to place Software Testing on an equal footing, a second “V” dedicated to Testing is integrated into the model. Both “V”s together give the “W” of the W-model. So the connection between the various test phases and the basis for Testing is quite clear. In the W-model the significance of the tests and the ordering of the individual activities for Testing are quite clear. Parallel to the development process, in a tighter sense, the Testing process is carried out.
At the beginning of the project the test activities must start. Establishing a test strategy aligning to the process followed, draw up a test plan and approach for the project, determine adequacy of test coverage and test intensity, organise the test team, establish monitoring and Test Reporting.
Although we won't cover Waterfall model as part of Manual Testing Training, it is worth taking a quick look at this legacy development model used in life critical testing projects. One of the first models for software development is waterfall model. In this model it is set out that each of the activities in the software development must be completed before the next can begin. A return to the development process was only possible to an immediate previous phase. By this model it was suggested that activities for testing could first be started after the implementation.