Request: Mark results from test projects (and option to exclude)
Search everywhere is a very great tool to find anything without navigating through 100s of projects and folders (or even files). The same is true for ‘Usages’ to follow the execution path.
With increasing number of tests for almost every file and method, you end up with search results that are mostly tests or test related files.
We need a visual mark for faster understanding if the entry is only used in tests (and so not related for most searches). An option to quickly exclude all these results would be of great help too.
Example: Dto file, most of shown results are tests or test only helper classes
Example: Generate method, only used in one place outside of tests
Because (in most cases) all test related files are in separate test projects, it should be relative easy to figure out if a file is test related
Please sign in to leave a comment.
Hello,
Unfortuately your requirements are not natively supported by Search Everywhere or Usage feature. Here are a couple of alternative approaches you can try:
If these alternatives don't fully meet your needs, we encourage you to submit a feature request on our issue tracker. This allows others to view your request and add their votes if they find the feature useful.
Regards,
Tom
Tom Luo Thanks for your response - searching in specific project is not practicable in an mono repository. Usage is great but only for more advance search (a lot slower to work with) - in your quick search you want to exclude tests most of the time.
There are a few issues for this features, the “original” issue i could find is 6 years but the number of likes, comments and linked issues doesn't reflect how many people are looking forward to something like this. There a so many “alike” features that have the same intention but slightly different approach. So there is big demand for this!
Would be great if it can be combined together. Some of these are 12 years old… and still nothing has happen (toward this problem/feature) in these 12 years
Here are a few related issues:
As mentioned, none of these issues are linked together although they describe the same feature - so please give this the attentions it deserves.
Thank you for sharing your valuable insights.
I’d like to assure you that we have a structured process in place to track and categorize such requests—the issues are usually organized in our issue tracker using “subsystem” field and tags for better visibility.
Your suggestion aligns well with our existing strategy: when planning future goals, we review all relevant requests and evaluate how they fit into our roadmap. Where possible, we aim to consolidate related needs into a broader solution.
Regarding the specific issues you raised, I’ve already brought them to the attention of our development team. They will reassess the priority and take appropriate action.
We appreciate your engagement.
Thanks,
Tom