Home › Software Testing › Software Testing › advanced_security_performance › Fuzz testing (fuzzing) inputs are typically
Fuzz testing (fuzzing) inputs are typically
AProduction data anonymised by hashing
BSynthetic data for analytics dashboards
CMalformed or random data to find crashes
DCarefully crafted valid happy paths
Answer & Solution
Correct answer: C. Malformed or random data to find crashes
Fuzzers (AFL, libFuzzer, OSS-Fuzz) inject random/malformed/grammar-aware inputs to trigger crashes, hangs, memory errors. Coverage-guided fuzzing (AFL) evolves inputs to maximise code coverage.
Related questions
Test coverage is BEST described asContinuous Testing in DevOps meansIn the V model of SDLC, system testing corresponds to'Test data' management addressesIn ISTQB terminology, a 'test oracle' isAcceptance Test Driven Development (ATDD) emphasisesTest Driven Development uses the rhythm ofRecovery testing simulates