Source

pytest.el / pytest.el

Author Commit Message Labels Comments Date
Tom Davis
Use relative paths to test files to fix fixture discovery. When we cd to the project directory then supply the full root path to tests (in the case of pytest-run-module, etc.) pytest gets confused and cannot find custom fixtures.
Eric Larson
Make sure you can change pytest-global-name via dir locals. Make `runtests` the initial pytest-project-names.
Eric Larson
Using py.test as the command line executable as it seems to always be available
Eric Larson
If we are not in a buffer that is a file, then use the default directory as a base for our prompt.
Eric Larson
Switched to a model of constructing command line flags instead of specific variable flags. I added a pytest-run command that will prompt you for pytest running details and run it in compilation-mode.
Eric Larson
version bump
Tags
0.2.1
Eric Larson
Added customize support
Eric Larson
version bump
Tags
0.2.0
Eric Larson
simplified the cmd formatting
Eric Larson
removed pattern of adding variables for each command flag in favor of a simple string setting for all the flags
Eric Larson
fixed comment
Eric Larson
fixed up the preceding comments to make sure the package is valid
Eric Larson
Added support for running all the tests in a directory
Eric Larson
Support for --assert=plain option
Eric Larson
Added the -x flag when looping on failing
Eric Larson
Added support for xdist looponfailing and adjusted it so we change to the project root before running the test runner
Eric Larson
initial commit of my port of nosemacs for pytest