Issue# 405: New test case for previously missed code in fastani

[baileythegreen]

Addition of a new test case to address some previously uncovered code.

Closes #405.

Type of change

(not quite a bug fix, really, but this is the closest option)

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality not to work as expected)
• This change requires a documentation update
• This is a documentation update

Action Checklist

• Work on a single issue/concept (if there are multiple separate issues to address, please use a separate pull request for each)
• Fork the pyani repository under your own account (please allow write access for repository maintainers)
• Set up an appropriate development environment (please see CONTRIBUTING.md)
• Create a new branch with a short, descriptive name
• Work on this branch
  • style guidelines have been followed
  • new code is commented, especially in hard-to-understand areas
  • corresponding changes to documentation have been made
  • tests for the change have been added that demonstrate the fix or feature works
• Test locally with pytest -v non-passing code will not be merged
• Rebase against origin/master
• Check changes with flake8 and black before submission
• Commit branch
• Submit pull request, describing the content and intent of the pull request
• Request a code review
• Continue the discussion at Pull requests section in the pyani repository

[widdowquinn]

"file location" maybe isn't specific enough, here. I propose changing to "path to fastANI executable"

[widdowquinn]

Looks good, but please see the comment in fastanai.py

[baileythegreen]

I closed this PR because I decided it wasn't quite right. See my comment here: #405 (comment).