alfredodeza/pytest.vim issues and pull requests

#80 - Feature request: a flag to open test output right away

Issue - State: closed - Opened by devenv over 1 year ago - 1 comment

#79 - Add pytest_extraflags configuration option

Pull Request - State: open - Opened by MarceColl almost 2 years ago

#78 - `:Pytest function` doesn't work with nested functions

Issue - State: closed - Opened by dwhswenson about 3 years ago - 4 comments

#77 - video in the readme unrated

Issue - State: open - Opened by con-f-use about 3 years ago - 1 comment

#76 - include stderr from conftest in async and catch error with regex

Pull Request - State: closed - Opened by alfredodeza over 3 years ago

#75 - Do not override global vars that config test location

Pull Request - State: closed - Opened by vecin2 over 4 years ago - 1 comment

#74 - Configurable project test directory

Issue - State: closed - Opened by vecin2 over 4 years ago - 4 comments

#73 - Runtime arguments not sent to :Pytest project

Issue - State: closed - Opened by leblancfg over 4 years ago - 6 comments

#72 - `Pytest <action> -s` should open a new window

Issue - State: closed - Opened by wookayin over 4 years ago - 7 comments

#71 - fails to parse when no exceptions/assertions are reported

Issue - State: open - Opened by alfredodeza over 4 years ago
Labels: parsing

#70 - Add support for pytest-pudb

Issue - State: closed - Opened by tuxxy over 5 years ago - 5 comments

#69 - Fails to parse with SystemExit

Issue - State: open - Opened by alfredodeza over 5 years ago

#68 - ImportError breaks parsing

Issue - State: closed - Opened by alfredodeza almost 6 years ago

#67 - pytest command not configurable

Issue - State: closed - Opened by rsnyman about 6 years ago - 5 comments

#66 - SyntaxError causes no session, breaks reporting

Issue - State: closed - Opened by alfredodeza over 6 years ago

#65 - Feature request: statusline function

Issue - State: open - Opened by JakobGM over 6 years ago - 2 comments

#64 - Add documentation for tweaking jump behaviour

Issue - State: closed - Opened by JakobGM over 6 years ago - 7 comments

#63 - `looponfail` continues to run tests after everything passes

Issue - State: closed - Opened by OddBloke over 6 years ago - 3 comments

#62 - "Undefined variable: a:3" during looponfail run

Issue - State: closed - Opened by OddBloke over 6 years ago - 2 comments

#61 - support for extra_flags and pdb extra_flags support

Pull Request - State: closed - Opened by joetsoi almost 7 years ago - 4 comments

#60 - Unable to specify where to find the py.test command

Issue - State: closed - Opened by joenye almost 7 years ago - 1 comment

#59 - Failing to parse when warnings are all over

Issue - State: closed - Opened by alfredodeza almost 7 years ago - 1 comment

#58 - fails on decorated methods

Issue - State: closed - Opened by davidszotten almost 7 years ago - 9 comments

#57 - Is there any support for unittest

Issue - State: closed - Opened by kraxli about 7 years ago - 2 comments

#56 - looponfail when write not test file

Issue - State: closed - Opened by jaesbit about 7 years ago - 1 comment

#55 - Feature Request: Open next error in the same window rather than a split

Issue - State: closed - Opened by dunk about 7 years ago - 4 comments

#54 - :Pytest method not working

Issue - State: closed - Opened by jaesbit about 7 years ago - 5 comments

#53 - Support to run on save

Issue - State: closed - Opened by jaesbit about 7 years ago - 3 comments

#52 - Consider allowing setting the debugger

Issue - State: closed - Opened by alok about 7 years ago - 2 comments

#51 - open terminal in new split for test

Issue - State: closed - Opened by jwkvam about 7 years ago - 2 comments

#50 - Broken on Neovim stable

Issue - State: closed - Opened by decko over 7 years ago - 3 comments

#49 - Use ipdb or ipython capabilities when available.

Issue - State: closed - Opened by decko over 7 years ago - 3 comments

#48 - Added two global variables to configure project test directory and test file

Pull Request - State: closed - Opened by pmacosta almost 8 years ago - 3 comments

#47 - broken on Neovim

Issue - State: closed - Opened by alok almost 8 years ago - 12 comments

#46 - Include a guide on how to install this

Issue - State: closed - Opened by BenNewsome about 8 years ago - 3 comments

#45 - Why not feed the location list with the errors found?

Issue - State: closed - Opened by josefson about 8 years ago - 3 comments

#44 - `Pytest function` files for marked functions.

Issue - State: closed - Opened by DerWeh about 8 years ago - 5 comments

#43 - Check for method declarations across multiple lines.

Pull Request - State: closed - Opened by joetsoi over 8 years ago - 1 comment

#42 - Fix method calls with pdb

Pull Request - State: closed - Opened by joetsoi over 8 years ago - 2 comments

#41 - plugin isn't being loaded for python files for me

Issue - State: closed - Opened by dgoldstein0 over 8 years ago - 4 comments

#40 - Running :Pytest file fails on files with spaces in their paths

Issue - State: closed - Opened by D-Vaillant over 8 years ago - 4 comments

#39 - Easily re-run failed tests

Issue - State: closed - Opened by bradgrimm over 8 years ago - 3 comments

#38 - Fix crash when running project tests

Pull Request - State: closed - Opened by alexlafroscia almost 9 years ago - 1 comment

#37 - Can't specify name of alternative test directory

Issue - State: closed - Opened by dbedrenko almost 9 years ago - 4 comments

#36 - if skipped tests are shown, don't say all tests passed

Issue - State: closed - Opened by alfredodeza almost 9 years ago

#35 - enable full neovim support for async tests

Issue - State: closed - Opened by alfredodeza almost 9 years ago - 1 comment

#34 - neovim support when using `--pdb` or `-s`

Issue - State: closed - Opened by alfredodeza almost 9 years ago - 1 comment

#33 - Allow to pass options to py.test

Issue - State: closed - Opened by blueyed almost 9 years ago - 10 comments

#32 - Fails with spaces in file path

Issue - State: closed - Opened by alexlafroscia about 9 years ago - 8 comments

#31 - `No failed tests from a previous run` lies

Issue - State: closed - Opened by alfredodeza about 9 years ago - 2 comments

#30 - Shows all tests passed instead of fail.

Issue - State: closed - Opened by ev-agelos about 9 years ago - 11 comments

#29 - Make pytest run doctests as well

Pull Request - State: closed - Opened by fabianvf about 9 years ago - 12 comments

#28 - Is there any support for doctests?

Issue - State: open - Opened by fabianvf about 9 years ago

#27 - Most exceptions do not display the exception message

Issue - State: closed - Opened by alfredodeza over 9 years ago - 1 comment

#26 - pytest-sugar

Issue - State: closed - Opened by vigten over 9 years ago - 9 comments

#25 - fix testing with nested classes and methods

Pull Request - State: closed - Opened by alfredodeza almost 10 years ago

#24 - Cannot run test classes with inner classes

Issue - State: closed - Opened by sloria almost 10 years ago - 6 comments

#23 - Can't run function/method that uses parametrization

Issue - State: closed - Opened by sloria almost 10 years ago - 14 comments

#22 - Add --color=no to py.test cmd

Pull Request - State: closed - Opened by yarbelk almost 10 years ago - 3 comments

#21 - :Pytest project always returns "no failed test from a previous run" unless current buffer is in tests dir

Issue - State: closed - Opened by ecerulm about 10 years ago - 7 comments

#20 - `looponfail` has undefined variables

Issue - State: closed - Opened by alfredodeza over 10 years ago - 6 comments

#19 - py.test -s with conque doesn't clean up the buffer

Issue - State: closed - Opened by ryanpetrello over 10 years ago - 1 comment

#18 - Nested functions cause the plugin to fail

Issue - State: closed - Opened by nicolaiarocci over 10 years ago - 3 comments

#17 - "function" is missing from autocompletion

Issue - State: closed - Opened by brettc almost 11 years ago - 3 comments

#16 - Allow to "just" run py.test in the current working directory

Issue - State: closed - Opened by blueyed almost 11 years ago - 4 comments

#15 - Passing custom arguments to py.test

Issue - State: closed - Opened by ktosiek about 11 years ago - 2 comments

#14 - Add a "project" argument to Pytest.vim

Pull Request - State: closed - Opened by bstinsonmhk about 11 years ago - 4 comments

#13 - `:Pytest file delgado` requires redraw for terminal vim

Issue - State: closed - Opened by shaunduncan over 11 years ago - 2 comments

#12 - quote file path

Pull Request - State: closed - Opened by yec almost 12 years ago - 1 comment

#11 - Doesn't work when vim's current directory isn't the same as the test's file directory.

Issue - State: closed - Opened by donvargax over 12 years ago - 7 comments

#10 - Green bar when py.test not installed

Issue - State: closed - Opened by ryanpetrello over 12 years ago - 2 comments

#9 - Fixed issue #8, added an augroup to guard looponfail autocmds

Pull Request - State: closed - Opened by pyx over 12 years ago - 2 comments

#8 - LoopOnFail and LoopProxy may remove autocmd set by other scripts

Issue - State: closed - Opened by pyx over 12 years ago

#7 - :Pytest error error

Issue - State: closed - Opened by totte almost 13 years ago - 4 comments

#6 - Fix to make zz work even if remapped

Pull Request - State: closed - Opened by totte almost 13 years ago

#5 - Adds global variables for command and path delimiters

Pull Request - State: closed - Opened by ameade almost 13 years ago - 3 comments

#4 - can't provide alternative py.test

Issue - State: closed - Opened by mrsipan over 13 years ago - 4 comments

#3 - can't give path of alternative py.test

Issue - State: closed - Opened by mrsipan over 13 years ago

#2 - calling pytest is blocking

Issue - State: closed - Opened by RonnyPfannschmidt over 13 years ago - 3 comments

#1 - :Pytest function doesnt seem to act on parametrized functions

Issue - State: closed - Opened by RonnyPfannschmidt over 13 years ago - 3 comments

GitHub / alfredodeza/pytest.vim issues and pull requests