A method whereby purposely inserted erros into a
programming code under test to verify that the detect the
defect. It is also known as error seeding.
comments please......
Poonam,
I think lot of diff is there between debugging and mutation.
i deffinetely consider you and suneel suggetions, today i
will discurse with my team and i will let you know.
Thanks,
Ashok
A testing methodology in which two or more program mutations
are executed using the same test cases to evaluate the
ability of the test cases to detect differences in the
mutations.
or
A method whereby errors are purposely inserted into a
program under test to verify that the test can detect the
error. Also known as error seeding.
or
A method to determine test set thoroughness by measuring the
extent to which a test set can discriminate the program from
slight variants of the program. Non-intrusive Testing:
Testing that is transparent to the software under test; ie,
testing that does not change the timing or processing
characteristics of the software under test from its behavior
in a real environment. ...
oh!!!! Kewl the topic now entered into Debugging!!!! :-)
After the initial testing is complete, mutation testing is
taken up. The idea behind mutation testing is to make a few
arbitrary small changes to a program at a time, each
time the program is changed it is called a mutated program;
the change is called a mutant.
A mutated program tested against the full test suite of the
program. If there at least one test case in the test suite
for which a mutant gives an incorrect result, then the
mutant is said to be dead.
If a mutant remains alive even after all test cases have
been exhausted, the test suite is enhanced to kill the
mutant.
The process of generation and killing of mutants can be
automated by predefining a set of primitive changes that
can be applied to the program.
The primitive changes can be:
? Altering an arithmetic operator,
? Changing the value of a constant,
? Changing a data type, etc.
A major disadvantage of mutation testing:
? computationally very expensive,
? A large number of possible mutants can be generated.
Valid?????? :-)
Mutation test means a change in your program programmers
are perform changes in tested programs to estimate
completeness and correctness of the program testing
Hi,
In the mutation testing we create the mutants(duplicate
copy) and then we test on the mutants and finds whether any
difference is there between the mutants and the original
program after the test.
Plz comment if i m wrong......
nitin9360@yahoo.com
Mutation means a change in a program. Programmers are
performing changes in programs to estimate correctness of
testing coverage.
For eg: one test passed, then apply certain change in that
particular program and test it... if the result is failed
then we can say it as a mutation testing i.e a change
should affect the result ..
straight,Purposefully introducing the bug in the
application and checking the the variation in the expected
result. this is Mutation testing or bebugging, No
confusions.
Just remember we are intentionally introducing the bug......
Mutation means a known change in a program. during this
testing developers will check whether all modules are
participating or not while executing the program.
The project is going through the maintainance phase I
logged a defect which is critical for resolving ,the
developement team is in US when they got the reported bug
they gave the xplanation that it is a six year old written
code moreover we don't have proper followup documents to
authenticate this one....in this senario wat will u do??
one deffectis found then we send it to the developers.and
they released a new build.What we test in that build?The
whole application or the only test cases where we got the
deffect.
After project was released to customer the customer find a
defect in u r build. the build is related to that area which u
had tested that. so u r TL comes and asks u then how will u
convince u r TL and The customer
If we got build [say 2.0]to test, we test it & maintain the
log then we got same build [say 2.0] fixing bugs in the
same version 2.0 again we test it .My question is How we
maintain this second log of testing same build