-
-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot jump to tests from test report #921
Comments
Option 1 seems pretty sensible to me. |
P.S. We really need to develop some integration tests for CIDER, as such trivial regressions are relatively common. Pretty much nobody uses all of the features and often some change causes breakages that aren't noticed at all for a while. |
@llasram How's that PR coming along? :-) |
Commit b130451 broke non-interactive use of `cider-jump-to-var`, which in turn broke `cider-test-jump`. This commit fixes the former issue and thus also fixes the latter.
Opened. I was looking into Emacs integration testing, but then the US holiday season ended and I'm back to my primary projects. So no integration tests yet, but at least this feature restored. |
[Fix #921] Non-interactive `cider-jump-to-var`.
Guess we can open a separate ticket dedicated to integration tests. I think the |
Actually we never could get integration tests with ecukes to work. We're mocking out responses from the middleware instead, which is far less useful imo. My recommendation is to stay away from ecukes and just write integration tests using |
Invoking
cider-test-jump
from the test report (as default-bound tot
) does not jump to the test. Instead it just always yields the message 'Symbol SYMBOL not resolved', where SYMBOL is whatever symbol is under point.Commit b130451 appears to have broken non-interactive calls to
cider-jump-to-var
, wherecider-test-jump
seems to contain the only such instance in CIDER proper. I'm willing to write a PR to fix this, but I'm not sure which is correct approach: (1) fixcider-jump-to-var
to once more support non-interactive invocation, (2) fixcider-test-jump
to e.g. usecider--jump-to-loc-from-info
directly, or (3) both.Thanks!
The text was updated successfully, but these errors were encountered: