Software Testing Basics

Software Testing Basics: Software testing is a process to check the quality of the software and to reduce the risk of software failure in operation. To execute the application/program with the intent of finding bugs.

Software testing is a process that includes various activities like:

• Review of SRS document
• Test Planning
• Test Case Designing
• Execution of Test Plan
• Execution of Test Cases
• Bug Reporting

Static Testing: A testing technique that is used to test the system without code execution is called static testing.

Dynamic Testing: Testing that involves the execution of a component or system being tested is called dynamic testing.

“Testing also includes reviewing the requirements, user stories, and source code.”

Software Testing also used to validate the System, which is checking whether the system will meet the user's requirements in its operational environment.

Testing and debugging are two different things. Testing is a process that finds defects in the software system. Debugging is done by the developers that find, analyze, and fix the defects.

Why Testing is Necessary?

Software testing is a necessary part to make an application defect free. The following are the main reasons why testing is necessary.

To produce a quality product
To make an application bug free
To meet the user requirements
To check that functionality is working fine
To check the performance of the application
To find out the defects that were made during development

What is Error?

A mistake in coding is called error. A mistake that is made by developers while developing a software component or system. This could happen because of the following reasons

Misunderstanding of software functionality
Miscalculation of values
Misinterpretation of any value

What is Bug/Defect?

An error that is found while testing an application is called a defect. In simple words the variance between the expected and actual result.
Defect or Bug report consists of the following information

Bug ID: Each bug contains a unique identification number.

Bug Title/Summary: A brief description of the bug.

Bug Description: Detailed information on the bug with reproduction steps.

Priority: It can be High/Medium/Low based on the urgency of bug.

Severity: It can be Critical/Major/Minor based on the impact of the bug on application.

Attachment: Screen-shots/Videos are attached for a better description of the bug.

Bug Life Cycle:

A cycle in which a bug goes through during its lifetime. This cycle contains many stages which are given below

New: When a bug is logged in any bug reporting tool, it is given a “New” state.

Assigned: When a bug is posted, then Developer lead or Manager assigns it to the available

developer. It is given an “Assigned” state.

Open: When a developer starts working on that bug, it goes into the “Open” state.

Fixed: When a bug is fixed by the developer then he makes the bug status as “Fixed” and the bug is passed to the testing team.

Retest: After the bug is fixed by the developer, tester retest the changes.

Verified: When a bug is passed by the tester, then the state of the bug changed to “Verified”.

Closed: After PM verification if things are going well, then it gave a state “Closed”.

Duplicate: If the same bug is logged twice or the two bugs mention the same concept of the bug, then one bug status changed to "duplicate".

Rejected: If a bug is not genuine, then the developer rejects the bug. Then the bug goes to the “rejected” state

Deferred: The state of the bug is changed to “deferred” when it does not belong to the current sprint”. It means it will be fixed in the next sprint.

Not a bug: The status is given as "Not a bug" if the tester reports a bug that is not in actual.

What is Failure?

The inability of the software to work in a production environment. The system deviates from the expected results.

Software Testing Basic Questions

What is software testing
Why is software testing important?
When should you do software testing?
How much testing is enough?
Why does software have defects?
When can we stop testing?
When should we start testing?
Can we make an application 100% bug-free?