Added File IO Testing

[auroq]

Congrats on taking the first step to contributing to the Sample Programs repository maintained by The Renegade Coder! For simplicity, please make sure that your pull request includes one and only one contribution.

Complete the Applicable Sections Below

Find which section best describes your pull request and make sure you fill it out. To start, let us know which issue you've fixed.

• I fixed #your-issue-number-here

Code Snippets

• I named the pull request using Added/Updated <Sample Program> in <Language> format
• I created/updated the language README
  • I added the sample program name to the README
  • I added fun facts (i.e. debut, developer, typing, etc.)
  • I added reference link(s) to the README
  • I added solution citations when necessary (see plagiarism)

Documentation

• I named the pull request using Added/Updated <Sample Program> in <Language> Article format
• I followed the applicable article template
  • I added/updated a language article (i.e. The Python Programming Language)
  • I added/updated a code snippet article (i.e. Hello World in Perl)
  • I added/updated a project article (i.e. Fizz Buzz in Every Language)

Testing

• I names the pull request using Added/Updated <Language>/<Project> Testing format
• I followed the testinfo template, if applicable

Notes

Feel free to describe what you added or updated.

[auroq]

In order to test File IO, I needed access to the output.txt file that is created at runtime, meaning that I needed access to the container itself.
In order to do that I added an exec method to Source, but I'm worried that could be abused. If we want to prevent abuse, I can get rid of the exec() method and replace it with a more specific get_file_text() method.

[jrg94]

Random idea: do you think it makes sense to pull your testing code out into its own repo? I was thinking it might be beneficial to start versioning your work and maybe even pip package it.

I can make a separate repo under The Renegade Coder (or you can use your own if you'd like).

[auroq]

Random idea: do you think it makes sense to pull your testing code out into its own repo? I was thinking it might be beneficial to start versioning your work and maybe even pip package it.

I can make a separate repo under The Renegade Coder (or you can use your own if you'd like).

That is something I have been considering as well.

Since it was originally pushed here, it is property of TheRenegadeCoder. However, with your consent, I would love to take ownership of it under my own name (but using the MIT license).

[jrg94]

Yeah, go for it! It's all your work after all. That way you can give it a cool name and whatnot. 👍

[jrg94]

I actually just used this GitHub tutorial today to create a new repo with all the history maintained (for a separate project).

[jrg94]

Adding this to the mix!