CodeScene has some test-specific smells that we detect. But other than that we do not differentiate between test code and application code. This is by design, as explained in the Software Design X-Rays book.
Some of the worst hotspots and design issues tend to be in automated tests. We have the application code we want to keep clean and easy to evolve, and the test code, which we know isn't part of our production environment, but if tests lack quality, they will hold us back. That's why we want to keep focusing the analysis efforts on test code, too. It's important to make sure the test code passes through the same quality gates (for example, code reviews and static analysis) as the application code.
However, as an organization, you can tailor code health to your needs. Our documentation has an example of how to customize the rules for test code: Customize the code health rules via JSON.