DenkzeitWiki

Unit Tests

GuiAutomation
ExtremeProgramming
WinYourBossForAutomatedTests

ReFactoring
LooseCoupling

CodeCoverage

DefensiveProgramming

MockObjects
DummyObjects?

A major motivation behind UnitTests is precisely to ensure that refactoring transformations do not break code. Good automated testing is a prerequisite of being able to refactor. And refactoring is a prerequisite of being able to adapt the structure of software to changing requirements.[1]

• Unittesten von regulären Ausdrücken

if it can break, test it [2]

• Wiki:UnitTestsDefined
• Wikipedia:Unit_test
  
• (interaktives) Testen von Java-Klassen und Programmen mit Jython: JythonSprache#JyUnit
  
• http://www-106.ibm.com/developerworks/library/j-test.html --Testing, fun? Really?
  Using unit and functional tests in the development process

Functional tests are written from a user's perspective. These tests confirm that the system does what users are expecting it to.

• http://jfunc.sourceforge.net/ --JFunc: JUnit Functional Testing Extension
  
  
• http://beust.com/weblog/archives/000303.html --Testing private methods? You bet.
  • Not really. Better test public-methods that invoke the private ones.
  
  
• http://rentzsch.com/links/shipleyOnUnitTesting --Shipley on Unit Testing
  
• Agile documentation in the Django project - UnitTests as documentation using PythonDoctest

generating documentation for your APIs from your unit test code

• Unit testing is an enabling technology
  
• http://ralfw.blogspot.com/search/label/Testen

Frameworks

Python

• http://pyunit.sourceforge.net/ --PyUnit
  • http://www.onlamp.com/pub/a/python/2004/12/02/tdd_pyunit.html
    • http://www.onlamp.com/pub/a/python/2005/02/03/tdd_pyunit2.html
  • http://docs.python.org/lib/module-unittest.html --unittest-Modul
  • http://diveintopython.org/unit_testing/index.html --Dive into Python - Erklärung von Unittesten
• http://dirtsimple.org/2005/08/ruby-gems-python-eggs-and-beauty-of.html --Ruby Gems, Python Eggs, and the beauty of unittest
• http://testoob.sourceforge.net/ --TestOOB: Advanced Testing in Python
  
  
• PythonDoctest -- Test interactive Python examples

• nose
• py.test
  • http://blog.ianbicking.org/pytest.html

Well, doctest is also very easy and cool; py.test makes all unit testing feel like doctest.

Java

• http://www.devx.com/Java/Article/26602 --Eclipse-JUnit-Tests in Jyton
  

• http://www.testingfaqs.org/t-unit.html --Unit Test Tools -collection

• JUnit
• NUnit

Test Sprech

• http://www.testingstandards.co.uk/living_glossary.htm --Glossary of testing terms

Test Case

A test case is a series of tests used to determine whether one particular thing works properly. [3]

Test Suite

A TestSuite can be used to run all of the tests in a TestCase. [4]

Text Fixture

books

• Softwaretests mit JUnit by Johannes Link
  • http://stmj.developertests.de/portal

Scratch

• Is unit testing doomed?
• http://www.developertesting.com/archives/month200801/20080128-SurveyOnBusinessBenefitsOfUnitTesting.html
• The benefits of automated unit testing
• Cost benefits of Unit Testing
  • http://www.developertesting.com/archives/month200501/20050127-TheDeveloperTestingParadox.html
• How Not to Evangelize Unit Testing
  • How to Evangelize Unit Testing
  • Excuses for Not Doing Unit Test
    
  
  
• It's OK Not to Write Unit Tests via TimBray
  • Many are beginning to discover that functional programming teaches far better design principles than unit testing ever will.
  • But then again, tests can have negative ROI. Not only do they cost a lot to write, they're fragile, they're always broken, they get in the way of your refactoring, they're always having you chase down bogus failures, and the only way to get anything done is to ignore them.
  • ~> test for regression
    
  
  
• http://s-expressions.com/2009/07/28/clojure-the-repl-and-test-driven-development/
• http://blog.objectmentor.com/articles/2009/06/05/rich-hickey-on-testing
  • think!
  • users are the test
  • In a functional language, where values are immutability and mutable state is handled in specific, principled ways, regressions don’t happen nearly as often.
• http://patricklogan.blogspot.com/2007/10/dynamic-languages-compilation.html
  
• http://patricklogan.blogspot.com/2003/07/test-first-is-command-line-interpreter.html

Test-driven design tools are "command line interpreters" for Java, C#, and other "non-interactive" programming languages.

Programmers using Lisp, Smalltalk, APL, and other "interpreted" languages have been doing test-driven design for decades. The pattern here is to type little snippets of code for an idea, get immediate feedback, then gradually incorporate those snippets into a whole program.
...
In either case, the end of a programming episode results in a transcript of code that is then allocated to two destinations... some of the code in the transcript are the objects or functions that go into the program itself. The rest of the code is edited into regression tests.
Looking at a test-driven incremental programming session using junit or nunit you see the very same result... the shell is the command line and xUnit is the "interpreter". You get a small idea, test it, and repeat.
The tests themselves are the "transcript" of the session, and are also the preserved regression tests.

testint private methods - 'violating' OO-design

• http://www.infoq.com/news/2008/01/private-methods-tdd-design
• http://www.khussein.com/tdd-testing-private-methods-using-aop/

white-box vs. black-box

• http://agiletesting.blogspot.com/2005/08/white-box-vs-black-box-testing.html

tests as specs

• Test or spec? Test and spec? Test from spec!