Tests needed for pdbtrack functionality
Some basic conditions to cover:
- Is pdbtracking automatically operational? Eg, when running a python program from an emacs interactive shell and a pdb prompt is encountered, does the pdbtracking detection trigger? (See issue #40 (closed) for an example of some interference that prevented proper operation.)
- Is "PDB" included in the buffer modelines while pdbtracking is active?
- When pdbtracking is operational and you step into code that has associated file paths and line numbers, does pdbtrack present the files and lines, with an overlay arrow indicating the correct line?
- As you tell pdb to step through the code, does the arrow advance accordingly?
- For target source files that do not already reside in emacs session buffers, does emacs fetch them when pdb advances into their code?
- When a pdb session concludes, is "PDB" properly removed from buffer modelines?
Some more complicated conditions:
- When running PDB sessions on remote systems, does pdbtrack properly seek the source files on those systems? (Be sure to test for fetching of remote Python source files that are not already present in an emacs session buffer, and that are not present in the same location on the emacs-session local filesystem. Both conditions can lead to a false success - see issue #44 (closed).)
- When PDB steps through synthesized code, for which there is no proper file to be found, or remote code for which you have no filesystem access (via, eg, rpdb), does pdbtrack properly utilize a python-mode buffer that has the same name as the file?