Difference between revisions of "Writing unit tests"

From Simson Garfinkel
Jump to navigationJump to search
m
 
Line 23: Line 23:
* [https://semaphoreci.com/community/tutorials/testing-python-applications-with-pytest Tutorial on fixtures and unit-testing with semaphore]
* [https://semaphoreci.com/community/tutorials/testing-python-applications-with-pytest Tutorial on fixtures and unit-testing with semaphore]
* [https://www.tutorialspoint.com/unittest_framework/unittest_framework_py_test_module.htm TutorialsPoint on pytest]
* [https://www.tutorialspoint.com/unittest_framework/unittest_framework_py_test_module.htm TutorialsPoint on pytest]
 
* [https://stackoverflow.com/questions/tagged/py.test StackOverflow questions on py.test]


== Other collateral ==
== Other collateral ==
* [https://www.toptal.com/qa/how-to-write-testable-code-and-why-it-matters Excellent article on Toptal about writing unit tests],
* [https://www.toptal.com/qa/how-to-write-testable-code-and-why-it-matters Excellent article on Toptal about writing unit tests],

Latest revision as of 09:07, 25 April 2018

Information on writing unit tests, from the Internet:

Key Concepts

  • Smallest testable unit
  • Test Cases
  • Test Discovery
  • Test Coverage
  • Test Driven Development / Test First Programming / Test First Development
  • Turning bugs into test cases
  • Integration Testing / Test on commit


General Guidance

  • When you write a function, immediately write the test. (Or, better, write the test before you write the function).
  • If function A creates a data object and then calls function B, which does something to the data object and then calls function C, it may be difficult to generate a test for each function. This may indicate that you should refactor your program. For example, you may wish to create a new class, AA, which has different methods for different data functions. You can then write tests for each of these methods.

Testing Python with py.test

Other collateral