Software testing

Software testing

software testing T0123434

What is testing?↵↵

Let's start by considering why testing is needed. Testing is necessary because we all make mistakes. Some of those mistakes are unimportant, but some of them are expensive or dangerous. We need to check everything and anything we produce because things can always go wrong - humans make mistakes all the time - it is what we do best! Because we should assume our work contains mistakes, we all need to check our own work. However, some mistakes come from bad assumptions and blind spots, so we might make the same mistakes when we check our own work as we made when we did it. So we may not notice the flaws in what we have done. Ideally, we should get someone else to check our work - another person is more likely to spot the flaws.

Simply what and how to check if your product is OK.

By knowing where you are and what you want. By using levels, techniques, types and time management

In simple words "T0123434"

T for testing 0 which refer to testing principal called " absence of error – fallacy " 1 for time management 2 are the static and dynamic testing 3 for techniques and 4 refer to number of testing types.

7 principals of testing

1-time management.

Time management is the process of planning and controlling how much time to spend on specific activities. Good time management allows an individual to complete more in a shorter period of time, lowers the amount of stress, and leads to career success.

2-static testing

Process

Planning

Initiate review

Individual review

Issue communication

Fixing and reporting

Role

Author

Management

Facilitator

Leader

Reviewers

Scribe

Type

Informal review

Walkthrough

Technical review

Inspection

Applying technique

Ad hoc

Checklist

Scenarios

Role-based

Perspective

3-Testing levels

SDLC

Requirement

Functional

High level design

Detailed design

V-Model

acceptance test plan

system test plan

integration test plan

unit test plan

STLC

Acceptance testing

System testing

Integration testing

Unit testing

                                                                  code

4-testing types

Functional – nonfunctional – structural – testing related to change

5-testing technique

Black box

Equivalent partitioning

Boundary value

Decision table

State transition

Use case

White box

Statement coverage

Decision coverage

Value between statement and decision

Experience based

Error guessing

Exploratory

Checklist