o NEg"@sFdZddlZddlZddlmZddlmZmZGdddejZ dS)acMachinery for running and validating transcripts. If the user wants to run a transcript (see docs/transcript.rst), we need a mechanism to run each command in the transcript as a unit test, comparing the expected output to the actual output. This file contains the class necessary to make that work. This class is used in cmd2.py::run_transcript_tests() N)Tuple)ansiutilsc@seZdZdZdZddZddZddZd d Zd e fd d Z de de fddZ e de de de dedee e e ff ddZdS) Cmd2TestCasezA unittest class used for transcript testing. Subclass this, setting CmdApp, to make a unittest.TestCase class that will execute the commands in a transcript file and expect the results shown. See example.py NcCs2|jr||jj|_t|jj|j_dSdSN)cmdapp_fetchTranscriptsstdout _orig_stdoutrStdSimselfri/var/www/eduai.edurigo.com/doc_train/edurigo_ai/Puru/venv/lib/python3.10/site-packages/cmd2/transcript.pysetUp#s  zCmd2TestCase.setUpcCs|jr |j|j_dSdSr)rr r r rrrtearDown+szCmd2TestCase.tearDowncCs6|jrt|j}|D] \}}|||q dSdSr)rsorted transcriptsitems_test_transcript)ritsfname transcriptrrrrunTest0s  zCmd2TestCase.runTestcCs:i|_|jjD]}t|}t||j|<|qdSr)rr testfilesopeniter readlinesclose)rrtfilerrrr 6s   zCmd2TestCase._fetchTranscriptsrc Cs`d}d}tt|}|d7}|s.||jjs9z tt|}Wn ty-d}Yn w|d7}||jjr|t|jjdg}zt|}Wn tyUd}Ynw|d7}||jjr| |t|jjdzt|}Wnty}z d ||d}t||d}~ww|d7}||jjsad |}|j |} |jj } d} t||jjrd |||| } ||  | || | qg} t||jjs| |zt|}Wn tyd}Ynw|d7}t||jjr| r||| d | } || } d |||| | } |t| | tjtjB| |rdSdS) NrFrTzGTranscript broke off while reading command beginning at line {} with {}zJCommand indicated application should quit, but more commands in transcriptz> File {}, line {} Command was: {} Expected: (nothing) Got: {} z7 File {}, line {} Command was: {} Expected: {} Got: {} )r strip_stylenext startswithrvisible_prompt StopIterationlencontinuation_promptappendformatjoinonecmd_plus_hooksr read assertTruestrip assertFalse_transform_transcript_expectedrematch MULTILINEDOTALL)rrrline_numfinishedlinecommandexcmsgstopresultstop_msgmessageexpectedrrrr=s                zCmd2TestCase._test_transcriptsreturncCsd}d} ||||d\}}}|dkr"|t||d7} |S|t|||7}|d}||||d\}}}|dkrM||||7}|d}n|t||dd7} |Sq)aParse the string with slashed regexes into a valid regex. Given a string like: Match a 10 digit phone number: /\d{3}-\d{3}-\d{4}/ Turn it into a valid regular expression which matches the literal text of the string and the regular expression. We have to remove the slashes because they differentiate between plain text and a regular expression. Unless the slashes are escaped, in which case they are interpreted as plain text, or there is only one slash, which is treated as plain text also. Check the tests in tests/test_transcript.py to see all the edge cases. r!rTFNr) _escaped_findr2escape)rrAregexstartfirst_slash_possecond_slash_posrrrr1}s$ z+Cmd2TestCase._transform_transcript_expectedrFrGin_regexcCs |d|}|dkr n?|dkrn:||d|dkrI|r.||||d7}|||7}n|t|||d7}|t||7}|d}nnq|||fS)aFind the next slash in {s} after {start} that is not preceded by a backslash. If we find an escaped slash, add everything up to and including it to regex, updating {start}. {start} therefore serves two purposes, tells us where to start looking for the next thing, and also tells us where in {s} we have already added things to {regex} {in_regex} specifies whether we are currently searching in a regex, we behave differently if we are or if we aren't. T/rCrr\)findr2rE)rFrArGrJposrrrrDs    !zCmd2TestCase._escaped_find)__name__ __module__ __qualname____doc__rrrrr strrr1 staticmethodintboolrrDrrrrrs@/.r) rRr2unittesttypingrr!rrTestCaserrrrrs