Scribd
Upload
19 views

Manual Testing Important Difference Between Questions

Uploaded by

Rely Neacsa
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
19 views

Manual Testing Important Difference Between Questions

Uploaded by

Rely Neacsa
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

MANUAL TESTING IMPORTANT DIFFERENCE

BETWEEN QUESTIONS
1) What is the difference between Static and Dynamic testing?

Static Dynamic
• It is a verification process. • It is a validation process.
• It involves different actives like • It involves different actives like
Requirement review, Design review, Functionality, Integration, System,
Code review, and Test case review, Adhoc, Smoke, Regration testing.
Test plan review.
• To do this we need not execute a • To do this we should run the
program. program.
• To do this we should have check list. • To do this we should have Test case.

2) What is the difference between Verification and Validation testing?

Verification Validation
• It involves process like review, walk • It involves actual testing.
through and inspection.
• It involves different actives like • It involves different actives like
Requirement review, Design review, Functionality, Integration, System,
Code review, and Test case review, Adhoc, Smoke, Regration testing.
Test plan review.
• We check whether are we building • We check whether are we building
product right. right product.

3) What is the difference between Functionality and Non-Functionality


testing?

Functionality Non-Functionality
• We test whether the application • Here we check whether the
works according to functional application works according to non-
requirement specification. functional requirement specification.
• Here we check whether software • Here we check whether look,
is working (or) not. performance is good (or) not.
• It involves different types of • It involves different types of
testing like Functionality, testing like useability testing,
Integration, System, Adhoc, Smoke, performance testing ( load,
Regration testing. stress, volume, soak) testing.
4) What is the difference between Retesting testing and Regration testing?

Retesting testing Regration testing


• Whenever developer gives build checking • Testing the unchanged feature to make sure
(or) verifying whether defect is fixed (or) that it is not affected (or) broken because of
not is called retesting. the changes here changes mean (adding,
modifying, removing (or) fixing the defect
regration testing
• Retesting is done for failed test case. • Regration testing done for passed test case.

• Retesting is planned. • Regration testing generic.


• Here we don’t go for automation. • Here we go for automation.

5) What is the difference between Priority and Severity?

Priority Severity
• Priority refers to the project and how urgent • Severity refers to the bug and how it Affects
it is solving the bugs. the user’s interaction with the applications.
• Priority is set based on changing project • Severity is objectively set based on the direct
factors e.g., the status of the bug, its and indirect impact of the bug and its
importance customer side. probability of occurrence

• Priority is a dynamic field, should be • Severity is usually a static field ( the only
revised and updated as the project reason to modify it would be if we learn
progresses. something new about the bug)

6) What is the difference between Error, defects and failures and Defects, root
causes and effects?

Error, defects and failures Defects, root causes and effects


• Time pressure • Customer complaints are effects.
• Misunderstandings about intra-system • incorrect interest payments
and inter-system interfaces, especially
when such intersystem and inter-system
interactions are large in number

7) What is the difference between Positive testing and Negative testing?

Positive testing Negative testing


• It is to determine what the system is • It is to determine what the system is not
supposed to do. It helps to check whether supposed to do. It helps to find the defects
the application is justifying the requirements from the software
or not.

You might also like