o DDi("@sdZddlZddlZddlZddlmZddlZddlmZddl Z ej j ddeddej j ej jgd ej dej j d ej dd ejjejjfd Gd ddejZedkrhej d edSdS)z Fuzz-tests for libCST, by Zac Hatfield-Dodds (zac@hypothesis.works) For Hypothesis documentation, see https://hypothesis.readthedocs.io/ For my Python code generator, see https://pypi.org/project/hypothesmith/ N) timedelta) from_grammarzsettings-for-unit-testsTi)seconds)name print_blobdeadlinesuppress_health_checkzsettings-for-fuzzingiʚ;)rparent max_examplesphasesc@s&eZdZdZeeej ddde j e dddde d d fd d Zeeej ddde j e d de jdde d d fddZeeej ddde j e dddddde d d fddZde de de d d fddZede de d d fddZede d d fddZd S)FuzzTestz0Fuzz-tests based on Hypothesis and Hypothesmith. HYPOTHESISFzHypothesis not requested file_input)start source_coderreturnNcCs4|j|dd||t|}|||jdS)aThe `from_grammar()` strategy generates strings from Python's grammar. This has a bunch of weird edge cases because "strings accepted by Cpython" isn't actually the same set as "strings accepted by the grammar", and for a few other weird reasons you can ask Zac about if you're interested. Valid values for ``start`` are ``"single_input"``, ``"file_input"``, or ``"eval_input"``; respectively a single interactive statement, a module or sequence of commands read from a file, and input for the eval() function. .. warning:: DO NOT EXECUTE CODE GENERATED BY THE `from_grammar()` STRATEGY. It could do literally anything that running Python code is able to do, including changing, deleting, or uploading important data. Arbitrary code can be useful, but "arbitrary code execution" can be very, very bad. execmodeN)reject_invalid_codereject_unsupported_codelibcst parse_module assertEqualcodeselfrtreerO/var/www/Datamplify/venv/lib/python3.10/site-packages/libcst/tests/test_fuzz.py&test_parsing_compilable_module_strings2s  z/FuzzTest.test_parsing_compilable_module_strings eval_inputcCsd|j|dd||zt|}|j|tg|ddWdStjy1t YdSw)zMuch like statements, but for expressions this time. We change the start production of the grammar, the compile mode, and the libCST parse function, but codegen is as for statements. evalrN) rrrparse_expressionverify_identical_astsModule code_for_nodeParserSyntaxError hypothesisrejectrrrr *test_parsing_compilable_expression_stringsPs    z3FuzzTest.test_parsing_compilable_expression_strings single_inputcCs|dddS)N )replace)srrr xszFuzzTest.cCsB|j|dd||t|}|j|tg|dddS)zJust like the above, but for statements. We change the start production of the grammar, the compile mode, the libCST parse function, and the codegen method. singlerN)rrrparse_statementr%r&r'rrrr )test_parsing_compilable_statement_stringsos    z2FuzzTest.test_parsing_compilable_statement_strings original_code rendered_coderc Cs<|dvsJ|ttj||dttj||ddS)N>r#rr2r)rastdumpparse)rr5r6rrrr r%s zFuzzTest.verify_identical_astsc Cs|dvsJt|z t|d|WdStyFttjtjtjd}z|||}d|}J|tyAt YnwJdw)zGInput validation helper shared by modules, statements, and expressions.>r#rr2z)r#rr2z2libCST parsed a string rejected by compile() into F unreachableN) r)notecompile Exceptiondictrr$rr3r*)rrparserrmsgrrr rs&       zFuzzTest.reject_invalid_codecCsd|vr tdSdS)a$ There are a few edge cases in Python that are too obscure and too hard to support reasonably. If we encounter code that is generated by Hypothesis which contains such features, we should reject it so we don't get failures that we aren't going to fix.  N)r)r*rrrr rs z FuzzTest.reject_unsupported_code)__name__ __module__ __qualname____doc__unittest skipUnlessboolosenvirongetr)givenrstrr!mapstripr+r4r% staticmethodrrrrrr r /sD    r __main__)rEr7rIrFdatetimerr) hypothesmithrrsettingsregister_profile HealthChecktoo_slowfilter_too_much load_profile get_profilePhasegenerateshrinkTestCaser rBmainrrrr s: