You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, minitest-emacs extracts the test description to pass as a regex to minitest. the minitest --name flag can take a string or a pattern.
For tests like it { assert true }, there is no string or pattern to pass from the test buffer. It appears that under the hood, minitest defines methods like test_0001_anonymous for these it blocks. The number determined by the order the test is defined in the file.
One way to potentially handle this is to use Emacs to parse the entire test buffer and build up a list of test definitions for the whole file. This could prove useful for other reasons, but may be complicated to accomplish, especially given the various ways that tests can be defined in the minitest ecosystem.
The text was updated successfully, but these errors were encountered:
@gcentauri@arthurnn
do you use minitest-emacs nowadays?
asking because I want to start using this - but if people have switched off or found alternatives then I might have second thoughts
@la-ruby - yes! I use it daily. I know the repo hasn't had much activity, but for most cases, everything just works. I'd like to get this into the non-gnu-elpa repo as well as MELPA, but yeah we're still here.
Currently, minitest-emacs extracts the test description to pass as a regex to minitest. the minitest
--name
flag can take a string or a pattern.For tests like
it { assert true }
, there is no string or pattern to pass from the test buffer. It appears that under the hood, minitest defines methods liketest_0001_anonymous
for theseit
blocks. The number determined by the order the test is defined in the file.One way to potentially handle this is to use Emacs to parse the entire test buffer and build up a list of test definitions for the whole file. This could prove useful for other reasons, but may be complicated to accomplish, especially given the various ways that tests can be defined in the minitest ecosystem.
The text was updated successfully, but these errors were encountered: