Skip to content

Conversation

@kaste
Copy link
Contributor

@kaste kaste commented Dec 7, 2018

If a user switches from test file to implementation file, it
is useful that 'Test Current File' remembers and executes the
actual last test file it ran.

Changes:

  • We actually match the filename against settings['pattern'].
    Not all files with a '.py' suffix are test files.

  • We store the last used test file in the window.settings()
    which is cheap to implement and probably the right thing.

  • Remove current_test_file property which was a misnomer and
    is now unused anyway.

If a user switches from test file to implementation file, it
is useful that 'Test Current File' remembers and executes the
actual last test file run.

Changes:

- We actually match the filename against `settings['pattern']`.
  Not all files with a '.py' suffix are test files.

- We store the last used test file in the `window.settings()`
  which is cheap to implement and probably the right thing.
@kaste
Copy link
Contributor Author

kaste commented Dec 7, 2018

For a test I would need to intercept a deferred call to super. This feels like it would take hours to get right.

@kaste
Copy link
Contributor Author

kaste commented Dec 7, 2018

I get a coverage 🔴 for that. 😒

@kaste kaste mentioned this pull request Dec 10, 2018
@randy3k randy3k closed this in #150 Dec 20, 2018
@kaste kaste deleted the remember-last-test-file branch December 20, 2018 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant