Current recommended testing approach

Hello Carson,

Yep, these ugly named classes are really the recommended approach to custom
language plugin testing. If you need to have custom project settings in your
test, you can override the getProjectDescriptor() method and use it to configure
your project.

So, if I was a guy helping write a plugin for a custom language, let's
call that language "Gosu", and I wanted to write some tests, what is
the general recommended approach for testing be?

Looking at the groovy plugin, which has been my guide to all things in
life, it appears that small extensions to the
LightCodeInsightFixtureTestCase and JavaCodeInsightFixtureTestCase is
the way to go.  I was thinking about simply pursuing the
LightCodeInsightFixtureTestCase approach, and being disciplined about
writing tests so they don't interfere with one another.  Is that a
viable approach?  Recommended?  Warned against?  Other thoughts?

No fair not answering me due to Kotlin. 

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"