Key Concepts in Software Testing

Bug

A mistake or defect in the software that causes it to work incorrectly.

Test Case

A detailed set of steps and conditions used to check if a feature works as expected.

Checklist

A simple list of things to check during testing, without detailed steps.

Regression Testing

Testing to make sure that new changes didn’t break anything that worked before.

Smoke Testing

A quick test to check if the basic functions of the software are working.

UI Testing

Testing the visual parts of the software (buttons, forms, layout).

UX Testing

Testing how easy and pleasant it is for users to use the product.

API Testing

Testing how different software systems communicate with each other through APIs.

Swagger

A tool used to view and test APIs; it shows what API endpoints are available and how to use them.

Postman

A tool for sending requests to APIs and checking their responses.

Bug Report

A document that describes a problem in the software, so developers can fix it.

Steps to Reproduce

Clear instructions on how to make the bug happen again.

Expected Result

What should happen if the software is working correctly.

Actual Result

What really happens when you test something (can be correct or show a bug).

Priority

Shows how fast a bug should be fixed (based on business needs).

Severity

Shows how serious the bug is (how much it affects the system).

STLC (Software Testing Life Cycle)

The step-by-step process for planning, designing, running, and ending testing activities.

SDLC (Software Development Life Cycle)

The process of planning, creating, testing, and delivering software.