Define Fuzz testing?
Answers were Sorted based on User's Feedback
Answer / guest
Hai...
Fuzz testing: Robustness Testing or Negative Testing is a
software testing technique that provides random data
("fuzz") to the inputs of a program. If the program fails
(for example, by crashing, or by failing built-in code
assertions), the defects can be noted.
almost all fuzz testing makes a record of the data it
manufactures, usually before applying it to the software,
so that if the computer fails dramatically, the test data
is preserved. If the fuzz stream is pseudo-random number
generated it may be easier to store the seed value to
reproduce the fuzz attempt.
K,Byeee...
Thanks & Regards
B.Ramyasri
Is This Answer Correct ? | 3 Yes | 0 No |
Answer / mfsi_krushnas
Fuzz testing or fuzzing is a software testing technique,
often automated or semi-automated, that involves providing
invalid, unexpected, or random data to the inputs of a
computer program. The program is then monitored for
exceptions such as crashes, or failing built-in code
assertions or for finding potential memory leaks. Fuzzing is
commonly used to test for security problems in software or
computer systems.
Is This Answer Correct ? | 2 Yes | 0 No |
1.what promted you to become involved in QA/Testing?
which document we prepare first whether test plan or test case document
Zenq interview questions for manual testing
What is Retesting & Regression Testing? When do we use retesting & regression testing(i.e In what situation)? Please clear me.
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.
can u give me the sample bug report
Which one is not tester responsibilities ? Option 1 Assure the process for contracting software is adequate Option 2 Review the adequacy of the contractors test plan Option 3 Perform acceptance testing on the software Option 4 Assure the ongoing operation and maintenance of the contracted software
in peer reviews,is there any checklist based on which we can review our team members documents.
Who is responsible for doing "Cause-Effect GraphCause Effect Graph". If tester is responsible then how we to do it? Urgent
what is a functionality
What is neutral test case?
what are the prerequisite conditins to test clientserver and web applications