Testing: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 21: Line 21:
* Lessons Learned in Software Testing: A Context-Driven Approach https://www.amazon.com/Lessons-Learned-Software-Testing-Context-Driven/dp/0471081124
* 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
* https://medium.com/@copyconstruct/testing-microservices-the-sane-way-9bb31d158c16
* Five Factor Testing https://www.devmynd.com/blog/five-factor-testing/

Revision as of 20:01, 8 March 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