Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Test directory not yet analysed #191

Closed
sophiajt opened this issue Mar 1, 2017 · 3 comments
Closed

Test directory not yet analysed #191

sophiajt opened this issue Mar 1, 2017 · 3 comments

Comments

@sophiajt
Copy link

sophiajt commented Mar 1, 2017

While we currently support #[test] functions, we don't yet analyse the files in the ./tests directory.

@sophiajt sophiajt added this to the Beta milestone Mar 1, 2017
@sophiajt
Copy link
Author

sophiajt commented Mar 7, 2017

We do get some RLS experience because autocomplete and goto-def fall back to racer. This should still be looked at, but removing the beta milestone since it's not as pressing as other issues.

@sophiajt sophiajt removed this from the Beta milestone Mar 7, 2017
@Xanewok
Copy link
Member

Xanewok commented Apr 1, 2017

Maybe we could piggyback on rust-lang/cargo#3431 when it's implemented. I assume that once the behaviour to test all targets is implemented in cargo, we could adapt it for analysing tests as well?

@Xanewok
Copy link
Member

Xanewok commented Nov 1, 2017

rust-lang/cargo#4592 this landed recently, so we might kill two birds with one stone (unit + integration tests)

@nrc nrc closed this as completed in 7fd2a0b Feb 15, 2018
nrc added a commit that referenced this issue Feb 15, 2018
Fix #191 check tests directory via 'all-targets' cargo flag
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants