Testing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 12: | Line 12: | ||
=Fundamentals and Conventions= | =Fundamentals and Conventions= | ||
* ''Access'' classes are BAD. Write test classes to belong the same package as the tested classes, this way package private functionality can be tested even if the test classes are physically in a different location. | |||
* A <tt>...TestBase</tt> is an abstract class that has a protected abstract <tt>get...ToTest()</tt> method. | |||
* If in developing a <tt>SomethingBase</tt> we want to test the base behavior at its own layer, then conventionally we should use a <tt>SomethingTestBase</tt> (and not a <tt>SomethingBaseTestBase</tt>). | |||
Revision as of 22:36, 2 May 2016
External
- Mutate Your Code and Reveal Your True Test Coverage http://www.infoq.com/presentations/code-mutate-test
- http://cafe.elharo.com/testing/harolds-corollary-to-knuths-law/
- Christian Nelson's SDForum JavaSIG presentation, Oct 6, 2009 File:Web Application Testing - Christian Nelson.pdf. Companion source code available at http://svn.carbonfive.com/public/christian/gearlist/branches/sdforum/. README file available at http://svn.carbonfive.com/public/christian/gearlist/branches/sdforum/docs/readme.txt.
- The Art of Software Testing at O'Reilly http://shop.oreilly.com/product/9781118031964.do
Internal
Fundamentals and Conventions
- Access classes are BAD. Write test classes to belong the same package as the tested classes, this way package private functionality can be tested even if the test classes are physically in a different location.
- A ...TestBase is an abstract class that has a protected abstract get...ToTest() method.
- If in developing a SomethingBase we want to test the base behavior at its own layer, then conventionally we should use a SomethingTestBase (and not a SomethingBaseTestBase).