Verifiaction:Means are we doing right thing.i.e we have to
check whether we are implementing right process.
validation:Means are we doing things right.i.e we have to
check whether we have developed a software as per the
client requirement.
Verification ensures that the application complies to
standards and processes. This answers the question " Did we
build the right system? "
Eg: Design reveiws, code walkthroughs and inspections.
Validation ensures whether the application is built as per
the plan. This answers the question " Did we build the
system in the right way? ".
Eg: Unit Testing, Integration Testing, System Testing and
UAT.
Varificatio:it is the process of confirming that s/w "meets
its specification".It involves reviews and meetings to
evaluate documents,plans,code,requirement and
specification.This can be done with checklist,issues lists
amd walkthroughs.
It is the examination of the process and checks r we
building the product right?
Validation:It is the process of confirming that it "meets
the user's requirements".Validation typically involves
actual testing and take place after varification are
completed.
Varificatio:it is the process of confirming that s/w "meets
its specification".It involves reviews and meetings to
evaluate documents,plans,code,requirement and
specification.This can be done with checklist,issues lists
amd walkthroughs.
It is the examination of the process and checks r we
building the product right?
Validation:It is the process of confirming that it "meets
the user's requirements".Validation typically involves
actual testing and take place after varification are
completed.
Verification takes place before validation,and not
viceversa. Verification evaluates
documents,plans,code,requirement and
specification.Validation evaluates product itself.The
inputs for verification are checklist,issues
lists,walkthroughs and inspection meetings,reviews and
meetings.The input for validation is actual testing of an
actual product.The output for verification is nearly
perfect set of documents,plans,specificationand requirement
document. The output of validation is nearly perfect product
Verification : 'Are we buliding a Product right?'it is a
static testing method.
Validation : 'Are we building a right Product?'it is a
Dynamic testing method.
verfication : A stage wise verfication of Design at
different stages thorugh test cases or reviews or any other
tool
validation: chekcing whether product designed meeting
client inputs and working as per the requirement It may be
validated by client or by practical validation on simulation
Verification -> Are we building product right?
Validation -> Are we building right product?
- Verification evaluates documents, plans, code,
requirements, and specifications.
- Validation, on the other hand, evaluates the product itself.
- The inputs of verification are checklists, issues lists,
walkthroughs and inspection meetings, reviews and meetings.
- The input of validation, on the other hand, is the actual
testing of an actual product.
- The output of verification is a nearly perfect set of
documents, plans, specifications, and requirements document.
- The output of validation, on the other hand is the
actual/perfect product.
=> Verification comes before Validation.
verification-
1 it emphasize on building the product right.
2 it is a low level activity.
3 it only checks the correspondence between a program and
its specification.
4 we do the Defect Testing to uncover errors.
validation-
1 it emphasize on building the right product.
2 it is a high level activity.
3 it checks that whether the software is operationelly
useful or not.
4 we do the Validation Testing to meet the customer
requirements.
verification is simlpy a method by whch we check that is we
are making the things right or not?means applying right
procedure or not,committing any mistakes or not and so on.
Validation is a process by which we check that is we are
making the right product or not,means the produt we are
making is as per as the client requirement or not.
Verification - Suppose, as per requirement we r supposed to
design a view with define number of values. So, to check
whether the view has that particular values on the view or
not.. this process is known as Verification. Verification of
Requirements.
Validation - Now, we need to test the view whether that
values defines on the view are functioning properly or not.
This process is known as Validation. Validation of
functionality.
Please correct me if I am wrong.
In the Testing, How do we find the Duplicate Defects. In
the case of testing is going on On-site r off-shore..some
times on site and off-shore people may enter defects at the
same time..those may include duplicate defects. how we have
to find those defects..
at the time of testing web based applications and client
server apllications, what you absorved as a tester? (i need
not differences, but i need what you absorved at the time
of testing as a tester)
Requirement is given : 1) The Login screen should require
with 2 fields "Login" & "Password"
2) After successful login
Success Message will display.
3) For Invalid login
Error Message will display.
4) "Login" & "Password"
both fields are case insensitive.
5) The Application should
be Dialog application.
What are the test cases for above requirements?
Hi, Below is a question on white box testing. Kindly help
me in answering it. How many test cases are needed to
obtain 100% branch coverage. This question was asked in
ISTQB foudation level exam - Dec21 2008.
Read(A,C)
If(A<10) then Print A;
Endif
If(C>100) then Print C is greater then A
else if(C<100) then print only C
Endif else
Options -
a. 4
b. 3
c. 2
d. 1
Kindly answer with explanation so that it would be easy to
understand
What would u do if u come across a bug...report it.....but
the programmer is in a diff location ( say u in India n he
is USA)..and he keeps accepting its a bug?