Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 4
    You are suggesting including test code (and additional inner classes) in the actual code of the package that is deployed?
    – user40980
    Commented Apr 11, 2013 at 3:36
  • 1
    The test class is an inner class of the class you want to test. If you don't want those inner classes to be deployed you can just delete the *Test.class files from your package. Commented Apr 11, 2013 at 7:49
  • 1
    I don't love this option, but for many it's probably a valid solution, not worth the downvotes.
    – Bill K
    Commented May 8, 2013 at 17:15
  • @RogerKeays: Technically when you do a deployment, how do you remove such "test inner classes"? Please don't say you cut them by hand. Commented Dec 13, 2013 at 10:54
  • I don't remove them. Yes. I deploy code that is never executed at run time. It really is that bad. Commented Dec 15, 2013 at 1:14