In this Software Testing Tutorial, we will learn about what is defect in software testing. Defects are also known as bugs and used interchangeably in any software development project. There is very minor difference between defect and bug which I will explain in further tutorials, however, in actual software testing projects you will find people using defects and bugs interchangeably and both refer to same thing.
Tag: software testing tutorial
Software Testing Tutorial #40 – Test Plan vs Test Strategy
In this Software Testing Tutorial, we will learn about the difference between test plan vs test strategy in software testing. A software test plan is defined at the project level whereas test strategy is at organization level. The test plan can change as per the requirement but the test strategy doesn’t change frequently.
Software Testing Tutorial#39-What is Test Strategy in Software Testing
In this Software Testing Tutorial, we will learn about what is test strategy in Software Testing. A software test strategy is a document which defines the broader and general way in which the testing will be approached within an organization. Test Strategy is mostly written at the organization level and is independent of projects. Project will use contents of test strategy and refine as per the project contexts.
Following are some of the key sections of test strategy document. Different organizations follow different templates but following sections are the key sections of test strategy document.
1. Scope and Environment
2. Testing Approach
3. Test Environment Specification
4. Testing Tools
5. Release Management
6. Risk Analysis
7. Reviews and Approvals
Software Testing Tutorial #38 – What is Test Plan in Software Testing
In this Software Testing Tutorial, we will learn about what is test plan in Software Testing. A software test plan document is the planning document which guide the software testing activities of the project.
The below mentioned Test Plan template is as per IEEE standards, different organizations follow different test plan templates as per their project needs. You can find many variations of Test Plan templates however all of them cover IEEE 829 standard items along with some additional points.
1. Test plan identifier
2. Introduction
3. Test items
4. Features to be tested
5. Features not to be tested
6. Approach
7. Item pass/fail criteria
8. Suspension criteria and resumption requirements
9. Test deliverables
10. Testing tasks
11. Environmental needs
12. Responsibilities
13. Staffing and training needs
14. Schedule
15. Risks and contingencies
16. Approvals
Software Testing Tutorial #37 – State Transition Testing Technique
In this Software Testing Tutorial, we will learn about state transition testing technique in software testing. When we test any software it can be defined in terms of state or finite-state machine.
Using the finite state machine for the application gives us clear picture of different states in which the application can transition and then derive the test cases for our testing. State transition testing is a black box test design technique which is used very widely and in this tutorial you will learn about state transition testing with examples.