1.

Difference Between Bug, Defect, and Error

Aspect Bug Defect Error

A flaw or deviation
A flaw in the A human mistake
from the
software's or omission in the
Definiti requirements found
functionality code or logic that
on by the end-user
identified causes incorrect
after the product is
during testing. behavior.
released.

Detected after
Detected during Occurs during
deployment,
Timing testing before coding or
typically by the end-
deployment. programming.
user.

Affects Indicates failure to

Often causes bugs
functionality meet specified
Impact or defects when
but not always requirements, often
unhandled.
critical. critical.

A login button Users report they

A programmer
does not cannot log in despite
Exampl mistakenly uses x
function as entering valid
e = x / 0, causing a
expected during credentials after
runtime exception.
testing. product launch.

2. Difference Between Authentication and Authorization

Aspect Authentication Authorization

The process of verifying The process of determining

Definition the identity of a user or the permissions and access
system. levels.

Determines "What you are

Purpose Confirms "Who you are."
allowed to do."

Focused on user privileges

Scope Focused on user identity.
and access control.

When It Before authorization, as

After authentication.
Happens a prerequisite step.
Aspect Authentication Authorization

Requires credentials Involves access control

Mechanism (e.g., username and mechanisms (e.g., roles,
password). permissions).

Logging into a system Accessing admin features in

Example using a username and a system only if you are an
password. admin.

3. Difference Between Validation and Verification

Aspect Validation Verification

Ensures the product Ensures the product is built

Definition meets user needs and correctly according to
requirements. specifications.

"Are we building the right "Are we building the

Purpose
product?" product right?"

Developer and testing

Focus End-user perspective.
perspective.

During or after
When It During development (e.g.,
development (e.g., UAT,
Happens code reviews, unit testing).
system testing).

Involves testing, user

Involves static testing,
Methods feedback, and
reviews, and walkthroughs.
prototyping.

Testing if the application Checking if the booking

Example allows users to book form is designed as per the
tickets easily. requirements.

4. Difference Between Black-Box Testing and White-Box Testing

Aspect Black-Box Testing White-Box Testing

Testing the software's Testing the internal logic

Definitio
functionality without and code structure of the
n
looking at the code. application.

Focus Functional testing (inputs Structural testing (how the

Aspect Black-Box Testing White-Box Testing

and outputs). code works).

Performe Testers who may not have Developers or testers with

d By coding knowledge. programming knowledge.

Manual testing tools,

Tools Code coverage tools like
automation frameworks like
Used JUnit, NUnit.
Selenium.

Checking if the login page Verifying if the login

Example accepts valid credentials function's code correctly
and rejects invalid ones. handles input validation.

5. Difference Between Alpha and Beta Testing

Aspect Alpha Testing Beta Testing

Testing performed by the Testing conducted by

Definition internal team (developers or real users in a production
QA) before release. environment.

Environme Done in a controlled, lab-like Done in a real-world

nt environment. environment.

Identifies major bugs and Gathers user feedback

Purpose ensures readiness for beta and finds edge-case
testing. bugs.

Developers, testers, and

Performed End-users or selected
sometimes internal
By external users.
stakeholders.

Internal testing of an e-
Users testing the app by
commerce app to ensure
Example making actual purchases
product categories display
and reporting issues.
correctly.

Examples for Clarity

Bug, Defect, and Error:

 Error: A typo in the code that causes a calculation to fail.

 Bug: During testing, a report shows that a search function

returns incorrect results due to that typo.
  Defect: A customer reports that search results are
inaccurate after product launch.

Authentication vs Authorization:

 Authentication: A user logs into a banking app by entering

their credentials.

 Authorization: Once logged in, the user can only view their
account details and is restricted from accessing admin
features.

Validation vs Verification:

 Validation: Checking that the app's UI is intuitive for users

during User Acceptance Testing (UAT).

 Verification: Reviewing the design documents to ensure that

all requirements are implemented correctly.

Black-Box vs White-Box Testing:

 Black-Box: Testing an ATM to ensure it dispenses cash

correctly when valid inputs are provided.

 White-Box: Checking the logic in the ATM's code to ensure

transactions are calculated correctly.

Alpha vs Beta Testing:

 Alpha: Developers test a new feature in a sandbox

environment.

 Beta: Real users try out the feature and provide feedback
before the final launch.

---------------------------------------

Differences Between Key Terms

1. Overriding vs Overwriting:

Overriding:

- Definition: A feature in object-oriented programming where a

subclass provides a specific implementation of a method that is
already defined in its parent class.

- Example:

```java

class Animal {
 void sound() {

System.out.println("Animal makes a sound.");

class Dog extends Animal {

@Override

void sound() {

System.out.println("Dog barks.");

```

- Key Point: Focuses on redefining behavior in inheritance.

Overwriting:

- Definition: Refers to replacing or modifying the content of a

file, variable, or memory location.

- Example:

```java

String data = "Old Data";

data = "New Data"; // Overwrites the old data with new data.

```

- Key Point: Related to replacing existing data, not tied to OOP.