Interested to Buy Any Domain ? << Click Here >> for more details...
Difference b/n Validation and verification?
- 8 Answers
- 13620 Views
- Amdocs, TSYS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / n@n!
verification/quality assurence/un conventional :
1)it is the procress of verifing that developers develop
right product r not.
2)verification is a prevention activity.
3)verification can be don through review and walk through.
validation/quality control/conventional:
1)it is the procress of finding bugs to make sure that
the application is work under customer expectations r not.
2)validation is a correction activity.
| Is This Answer Correct ? | 16 Yes | 4 No |
Answer / amit verma
Verification:- Are v builiding the product right??
-Verfication process is related with Quality assurance.
-Verification verifies whether the product is developed
right or not(include process & functionlty)
-It include reviews,code walkthrough,inspection.
Validation:- R v building the right product.
-Validation process is related with Quality Control
(Testing).
-Under this,test the application whether it is develop as
per as customer specification or not.
-In Validation phase,Testing process takek place.
| Is This Answer Correct ? | 8 Yes | 2 No |
Answer / vinay
validation is a process where we find that the product is
giving all the functionallity as per coustomer requirements.
verification is a process where we find that the product is
developing as per the customer requirement within following
the companys rules.
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / girish
Verification - (Are we building product right?)
For this-
1. Staic testing takes place in each & every phase of
project mang. life cycle (walk though, reveiws etc about
task)
2. We check that product making along with its
specification or not.
Validation - (Are we building right product?)
For this-
1. Dynamic Testing takes place in each & every madule when
completed. For testing we run each & every module.
2. Test these module & verfy those module work along with
its specification / customer expectation or not.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / sree
Verification is a process of cross checking, are we
developing a right product (s/w application) or not.
validation is a process of cross checking, whether the
developed product/application is right or not according to
the customer requirement.
| Is This Answer Correct ? | 4 Yes | 1 No |
Answer / srujana
Validation is evaluation of a system or component to
deteermine whether it meets the user neeeds or expectations.
-checking that we have built the right system?
Verification is evaluation of document or system to
determine whether it meets user requiremments.
-checking that we have buit the system right?
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / dipali1811
Validation only check the validity.Verification first veriefy
the program and correct mistakes if any present and then
validate the program.
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / bond
Verificatio: Testing application with out comparing the
output result with some value XXXX
Validation: Testing the application with comparing the
output with some value XXXX
| Is This Answer Correct ? | 4 Yes | 14 No |
What type of metrics we prepare in testing?
what are all requirements need for create gmail login page
what do u mean by Functional testing?
When are you done testing?
I have sent a mail through gmail.But it is not showing in the Sent mail option.Can any one tell me the defect description for this(asked for an interview)?
What is confirmation testing? Different between regression testing, confirmation testing and unit testing?
How you intearct with client in your organization ,plz give me real time scenario
May i know high priority&low seviarity,high seviarity&low priority
13 Answers DELL, GL Noble Denton, iGate, Wipro,
1.What kind of i/p we require from end user to start proper esting? 2.what's confirmation testing ? 3.Whats pilot testing ? 4. what's Defect cascading ? 5.Concept of work bench ?
What is Equivalance Class?
what is the difference between smoke, sanity and dry run testing?
I have to write test cases for Create User, Edit User, Delete User etc. Some of the steps for Create & Edit User are same. Then Should I write refer Create User [test case Id] for common test steps to write Edit User Test case? OR I have to write separate test steps even though they are repeatable in Create user & Edit User test case.
Automation Testing 
