Testing: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
(10 intermediate revisions by the same user not shown)
Line 3: Line 3:
* Mutate Your Code and Reveal Your True Test Coverage http://www.infoq.com/presentations/code-mutate-test
* 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/
* http://cafe.elharo.com/testing/harolds-corollary-to-knuths-law/
* Christian Nelson's SDForum JavaSIG presentation, Oct 6, 2009 [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].
* Christian Nelson's SDForum JavaSIG presentation, Oct 6, 2009 [[File:Web Application Testing - Christian Nelson.pdf|Web Application Testing - Christian Nelson]]. 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]
* The Art of Software Testing at O'Reilly http://shop.oreilly.com/product/9781118031964.do
* Testing the Endpoints of Your REST APIs https://www.infoq.com/presentations/rest-api-testing-postman


=Internal=
=Internal=
Line 12: Line 13:


=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>).
=To Process=
* Lessons Learned in Software Testing: A Context-Driven Approach https://www.amazon.com/Lessons-Learned-Software-Testing-Context-Driven/dp/0471081124
* https://medium.com/@copyconstruct/testing-microservices-the-sane-way-9bb31d158c16
* Five Factor Testing https://www.devmynd.com/blog/five-factor-testing/
* https://testing.googleblog.com/2013/07/testing-on-toilet-know-your-test-doubles.html
* Property-based Testing http://propertesting.com
* https://martinfowler.com/articles/practical-test-pyramid.html

Revision as of 02:04, 21 November 2018

External

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).

To Process