Programming.UnitTesting History

Hide minor edits - Show changes to output - Cancel

 
 
February 12, 2014, at 11:01 AM by MichaelPaulukonis - xrefs
Changed lines 44-45 from:
http://larsho.blogspot.com/2008/01/example-driven-development-and-unit.html
to:
[[http://larsho.blogspot.com/2008/01/example-driven-development-and-unit.html]]

Changed lines 48-49 from:
http://jasonrudolph.com/blog/2008/06/10/a-brief-discussion-of-code-coverage-types/
to:
[[http://jasonrudolph.com/blog/2008/06/10/a-brief-discussion-of-code-coverage-types/]]
Changed lines 51-54 from:
http://www.belshe.com/software/ - scroll down to see mention of [[http://sourceforge.net/projects/testlink/|Test Link]]
reff'd from http://discuss.joelonsoftware.com/default.asp?joel.3.577988

to:
[[http://www.belshe.com/software/]] - scroll down to see mention of [[http://sourceforge.net/projects/testlink/|Test Link]]
reff'd from [[http://discuss.joelonsoftware.com/default.asp?joel.3.577988]]

Changed lines 64-66 from:
http://the.artofunittesting.com/
http://tools.osherove.com/
http://www.manning.com/osherove/
to:
[[http://the.artofunittesting.com/]]
[[
http://tools.osherove.com/]]
[[
http://www.manning.com/osherove/]]
Changed lines 73-74 from:
to:
[[PHP.UnitTesting]]
[[PmWikiDevelopment.Testing]]
 
 
November 26, 2010, at 07:21 AM by OtherMichael - refactoring NUnit to its own page
Changed lines 54-60 from:
!! [@NUnit@] for C#
http://www.nunit.org/
[[http://www.dijksterhuis.org/setting-up-nunit-for-c-unit-testing-with-visual-studio-c-express-2008/|Setting up nUnit with Visual Studio Express]]
[[http://nunit.net/blogs/?p=28|Running NUnit Automatically in C# Express]]
[[http://nunit.net/blogs/|It's the Tests]] - a blog @ nunit.org
[[http://discuss.joelonsoftware.com/default.asp?joel.3.535744|C# NUnit Development Resources ?]]
Stack Overflow: [[http://stackoverflow.com/questions/tagged/nunit|questions tagged ''nunit'']]
to:
!! [@NUnit@] - for DotNet
see NUnit
 
 
November 18, 2010, at 07:12 AM by OtherMichael - nunit links
Added line 53:
Changed lines 55-60 from:
http://discuss.joelonsoftware.com/default.asp?joel.3.535744
to:
http://www.nunit.org/
[[http://www
.dijksterhuis.org/setting-up-nunit-for-c-unit-testing-with-visual-studio-c-express-2008/|Setting up nUnit with Visual Studio Express]]
[[http://nunit
.net/blogs/?p=28|Running NUnit Automatically in C# Express]]
[[http://nunit.net/blogs/|It's the Tests]] - a blog @ nunit.org
[[http://discuss.joelonsoftware.com/default.asp?joel.3.535744|C# NUnit Development Resources ?]]
Stack Overflow: [[http://stackoverflow.com/questions/tagged/nunit|questions tagged ''nunit'']]
 
 
August 31, 2009, at 12:16 PM by OtherMichael -
Changed lines 58-59 from:
FIT for Developign Software -- uses proprietary system
to:
FIT for Developing Software -- uses proprietary system

Added line 70:
[[Testing]]
 
 
September 22, 2008, at 04:20 PM by OtherMichael -
Changed lines 69-70 from:
InputAccel.UnitTesting
FormWare.UnitTesting
to:
 
 
June 12, 2008, at 10:34 AM by MichaelPaulukonis -
Added lines 45-47:

!! Code Coverage
http://jasonrudolph.com/blog/2008/06/10/a-brief-discussion-of-code-coverage-types/
 
 
May 19, 2008, at 09:49 AM by MichaelPaulukonis - Unit-tests as documentation
Added lines 4-16:
!!! Unit Tests as Documentation
[...] it's a good idea to design concrete examples of objects and scenarios before implementing the abstract classes.

Unit tests are exactly such examples. They make it easier to understand what happens at runtime. And a well designed unit test is the best way to explain to somebody what the code does. If you ever had to take over somebody else's code, you know how hard it can be to understand it. Where do you start? Unit tests is a good place to start.

So, my suggestion is to '''think of unit tests as documentation.''' Write unit tests that are easy to read and that explain the intent of the code.''[emphasis added]''

--http://larsho.blogspot.com/2008/05/use-examples-to-make-your-code-easier.html
>><<


>>clip lrindent<<
!!! Unit-tests make things go faster
Changed line 61 from:
Attach:Ch1_Unit_Testing.pdf - NOTE: crashes FoxIt reader, use Adobe or otherwise to print
to:
Attach:Ch1_Unit_Testing.pdf