Software Testing is method, technique or activity to find bugs.Where we check that software's actual result meets the expected result. Testing can be manually as well as using automation tools. Below are terms used in Software. Mainly differences that asked in Manual Software Testing Interview. Functional vs Non Functional , Re Testing vs Regression Testing , Front End Testing vs Backend Testing, Smoke Testing vs Sanity Testing , Static Testing vs Dynamic Testing, Verification vs Validation.

2. Contents Covered
• Functional vs Non Functional
• Re Testing vs Regression Testing
• Front End Testing vs Backend Testing
• Smoke Testing vs Sanity Testing
• Static Testing vs Dynamic Testing
• Verification vs Validation

3. Functional Testing Non Functional Testing
Checks the Product Feature. Checks the Product Properties.
Testing of functional requirement which defines a
system or its component.
Testing of non-functional requirement which
defines the quality attribute of a software system.
Function are mainly inputs, its behavior, and
outputs.
Quality attribute of a software system. Set of
standards used to judge the specific operation of a
system.
Captured in Use Cases. Captured in Quality Attribute.
Focus on User requirement . Focus on User expectation.
Easy to Capture Bugs. Tough to Capture Bugs.
Types of testing are System, Integration, End to
End, API testing, etc.
Types of testing are Performance, Stress, Usability,
Security testing, etc.

4. e
Re Testing Regression Testing
Performed for the Failed Test Cases and checks
that final execution is passed & defects are fixed .
Performed to confirm that recent code change has
not adversely affected existing functionality. Done
for passed test cases.
Defect Verification is part of Retesting testing. Defect Verification is not the part of Regression
testing.
Automation should not be done for Retesting. Automation can be or should be done for Regression
Testing.
Planned Testing. Generic Testing.
Checks for original fault has been corrected. Checks for unexpected side-effects
Executes a defect with the same data and the
same environment with different inputs with a
new build.
Done when there is modification or changes
become mandatory in an existing project

5. t
Front End Testing Back End Testing
Checks the overall functionality of application. Checks data loss, data corruption, deadlock etc.
Knowledge of Business requirement &
Automation.
Knowledge of SQL and Database.
No information required about Database storage. Information is required about Database storage.
Checks the Presentation Layer of 3 Tier
Architecture.
Performed on Database and Business Logic.
Types of Testing are : Unit Tests, Acceptance
Testing, Accessibility Testing, Regression Testing,
etc.
Types of Testing are : Database testing ,API
Testing, etc.
Performed on GUI . Element of web application,
front-end testing would involve checking
functionalities associated HTML, CSS and
JavaScript.
GUI not required . URI/URL can directly be passed
using a browser with the parameters required for
the function to get the response in some default
format. For Example, XML or JSON.

6. Smoke Testing Sanity Testing
Performed to check critical functionalities of the
program is working fine.
Performed to check the new functionality/bugs
that has been fixed or not.
Performed by Both Developers and Testers. Performed by Testers.
Smoke Testing is scripted and documented. Sanity Testing is neither scripted nor documented.
Considered as Subset of Acceptance Testing. Considered as Subset of Regression Testing.
Testing is performed from end to end. Testing is performed on certain components or
modules of the entire system.
Verification to check stability of the system in order
to proceed with more rigorous testing.
Verification to check rationality of the system in
order to proceed with more rigorous testing.
Smoke Testing similar to General Health Check up. Sanity Testing is similar to Specialized health
checkup.

7. Static Testing Dynamic Testing
Testing performed without executing the behavior
of the code.
Testing performed to check dynamic behavior of
the code.
Performed in early stage of development to avoid
errors or before compilation.
Performed after static testing or we can say after
compilation.
Testing of the software for checklist and process to
be followed.
Testing of the software for input values and output
values.
Performed for the Verification process. Performed for the Validation process.
Covers the Structural and Statement coverage
testing are forms of static testing.
Boundary Value Analysis & Equivalence
Partitioning are key techniques in Dynamic Testing.
Cost of Finding and Fixing defects is less But the
Return on Investment is high as it is involved in the
early stage .
Cost of Finding and Fixing defects is more But the
Return on Investment is low as it is performed
after the development stage .
Static Testing is for assessment of code and
documentation.
Dynamic Testing is for finding bugs/bottlenecks in
the software system.

8. Verification Validation
Basically focuses documents, design, code, and
program.
Basically dynamic mechanism of testing
and validating the actual product
Main Methods are walkthroughs, reviews,
inspections, and desk- checking etc.`
Main Methods are Black Box Testing, White Box
Testing, and non-functional testing
Does not include Execution of Code. Always includes executing of code .
Low level exercise and catches error that
validation cannot catch.
High level exercise and catches error that
verification cannot catch.
Assurance of product, service/ system to meet
need of customer & stakeholders.
Evaluation of whether or not a product/system
with a regulation, requirement & specification.
Done before Validation. Done After Verification.