Skip to content
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

Closed
llasram opened this issue Dec 21, 2014 · 6 comments
Closed

Cannot jump to tests from test report #921

llasram opened this issue Dec 21, 2014 · 6 comments

Comments

@llasram
Copy link
Contributor

llasram commented Dec 21, 2014

Invoking cider-test-jump from the test report (as default-bound to t) 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, where cider-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) fix cider-jump-to-var to once more support non-interactive invocation, (2) fix cider-test-jump to e.g. use cider--jump-to-loc-from-info directly, or (3) both.

Thanks!

@bbatsov
Copy link
Member

bbatsov commented Dec 21, 2014

Option 1 seems pretty sensible to me.

@bbatsov
Copy link
Member

bbatsov commented Dec 21, 2014

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.

@bbatsov
Copy link
Member

bbatsov commented Jan 10, 2015

@llasram How's that PR coming along? :-)

llasram added a commit to llasram/cider that referenced this issue Jan 10, 2015
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.
@llasram
Copy link
Contributor Author

llasram commented Jan 10, 2015

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.

bbatsov added a commit that referenced this issue Jan 10, 2015
@bbatsov
Copy link
Member

bbatsov commented Jan 10, 2015

Guess we can open a separate ticket dedicated to integration tests. I think the clj-refactor has some (and it has a similar structure - elisp + middleware), so we can borrow a bit of know-how from them.

@expez
Copy link
Member

expez commented Jan 11, 2015

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 ert.

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

No branches or pull requests

3 participants