Add more tests

[OrkoHunter]

• Whenever a new change is introduced, deploy the branch as a separate heroku app.
• The following flows must be tested
  • PR_FLOW
    • [x] Create a new PR involving Python files with errors without .pep8speaks.yml - https://github.com/OrkoHunter/test-pep8speaks/pull/81
    • [x] Create a new PR involving Python files with errors with .pep8speaks.yml - https://github.com/OrkoHunter/test-pep8speaks/pull/82
    • [x] Create a new PR which uses setup.cfg to read configurations. - https://github.com/OrkoHunter/test-pep8speaks/pull/83
    • [ ] Create a new PR involving Python files without errors without .pep8speaks.yml
    • [ ] Create a new PR involving Python files without errors with .pep8speaks.yml
    • [ ] Add a new commit to an opened PR with fixing the issues with .pep8speaks.yml
    • [ ] Add a new commit to an opened PR with fixing the issues without .pep8speaks.yml
    • [ ] Add a new commit to an opened PR with maintaining the issues with .pep8speaks.yml
    • [ ] Add a new commit to an opened PR with maintaining the issues without .pep8speaks.yml
    • [ ] Add a new commit to an opened PR with creating new issues with .pep8speaks.yml
    • [ ] Add a new commit to an opened PR with creating new issues without .pep8speaks.yml
  • Diff flow
    • [ ] Ask for diff on a PR with errors with .pep8speaks.yml
    • [ ] Ask for diff on a PR with errors without .pep8speaks.yml
    • [ ] Ask for diff on a PR without errors with .pep8speaks.yml
    • [ ] Ask for diff on a PR without errors without .pep8speaks.yml
  • pep8ify flow
    • [ ] Ask for pep8 fix on a PR with errors with .pep8speaks.yml
    • [ ] Ask for pep8 fix on a PR with errors without .pep8speaks.yml
    • [ ] Ask for pep8 fix on a PR without errors with .pep8speaks.yml
    • [ ] Ask for pep8 fix on a PR without errors without .pep8speaks.yml