download zip of files only
Tue Jan 31 00:14:39 HKT 2012
From /weblog/software_engineering/testing
The evil test: 1. Evil tests create a lock on how the code is implemented. 2. Cause duplication. 3. Builds uncertainty on the tests (red is meaningless). 4. Decrease productivity. 5. Discourage change. http://www.makinggoodsoftware.com/2012/01/27/the-evil-unit-test use thread in junit - http://softwareintegrityblog.com[..]blog/2007/11/05/false-positives-in-junit Don't try to test everything - http://www.nearinfinity.com[..]ay?entry=unit_testing_avoiding_extremism Why TDD fail? Because test is too complicate to write - http://agile.dzone.com/news/why-you-fail-tdd ( I agree it a lot ) Hard to test something? Unreadable tests? Slow running tests? It takes too long to write a test? Some solution suggested - http://www.stephenchu.com[..]/last-d-in-tdd-means-more-than-just.html Comment out test so that the code compile - http://martinfowler.com/bliki/TestCancer.html A list of TDD antipattern - http://blog.james-carr.org/?p=44 http://www.exubero.com/junit/antipatterns.html And the long discussion using random in unittest - http://tech.groups.yahoo.com[..]rivendevelopment/message/20458?var=1&l=1 Here is an example of using random in unittest, it actually same for every new instance! - http://www.skizz.biz/archives/000568.html Test abstraction smells - http://agileinaflash.blogspot.com[..]com/2011/11/test-abstraction-smells.html
(google search)
(amazon search)
Sun Oct 30 02:10:07 HKT 2011
From /weblog/software_engineering/testing
If you write the test after you've written the code, it's much more likely that you'll write the tests that will pass what you've written. That's just how our brains work. If you determine the criteria for whether a decision is good after you've already made the decision, it's much more likely that you'll create criteria that justifies the decision that was just made. That's just how our brains work. Determine how to assess whether something is good before you implement it and/or before you make a decision. Otherwise, you will tend to be emotionally attached to what you just did, what you just decided. http://jchyip.blogspot.com/2011/09/criteria-first.html My Top 5 ways to reproduce a "Hard to Reproduce" Bug! - http://software-testing-zone.blogspot.com[..]/my-top-5-ways-to-reproduce-hard-to.html Common TDD issue and suggested solution - http://www.agileadvisor.com[..]utomated-test-problems-address-root.html http://biblio.gdinwiddie.com[..]om/biblio/StudiesOfTestDrivenDevelopment http://www.notesfromatooluser.com[..]ptions-with-test-driven-development.html
(google search)
(amazon search)
Sun Sep 25 00:13:48 HKT 2011
From /weblog/software_engineering/testing
Customer attitude will affect how the software engineering workflow a lot: http://groups.yahoo.com[..]gprog/message/7420?threaded=1&var=1&p=24 Do you think this piece of code are too simple to have test case to cover? read this - http://gojko.net[..]t-the-software-craftsmanship-conference/ Related blog, finding the common between taking photo and software testing - http://andreas-simon.blogspot.com[..]hotographic-testing-lessons-learned.html . However, there is one big difference, it is harder to define a good photo than bug feel software If it is good to put developer as tester? - http://janetgregory.blogspot.com[..].com/2011/03/programmers-as-testers.html In fact I am kind of agree about this article, but maybe I just not TDD hard enough - http://beust.com[..]ectural-meltdown-around-iteration-three/ Tooling, Insight and Humility - http://www.developsense.com[..]reasons-for-testers-to-learn-to-program/
(google search)
(amazon search)
Thu Apr 28 00:36:26 HKT 2011
From /weblog/software_engineering/testing
Idea of how to refactoring test cases, summary : Refactor production code with the tests passing. This helps you determine that the production code still does what it is meant to. Refactor test code with the tests failing. This helps you determine that the test code still does what it is meant to. http://googletesting.blogspot.com[..]07/04/tott-refactoring-tests-in-red.html Collections of idea of testing private methods - http://www.infoq.com/news/2008/01/private-methods-tdd-design , may be it is a signal of refactoring? The other way of testing private , via compare with difference implementation - http://manversusvirtualmachine.blogspot.com[..]1/unit-testing-private-methods-like.html Explain the problem of non-Determinism in testing, common reason of why tests becoming non-Deterministic, and common solution - http://martinfowler.com/articles/nonDeterminism.html
(google search)
(amazon search)
Mon Jan 03 09:13:15 HKT 2011
From /weblog/software_engineering/testing
An simple example of doing javascript unit test - http://jroller.com[..]ray?entry=testing_javascript_with_groovy However this approach is too fake for me and easy to miss many thing, IMHO putting test a real environment is better A site for javascript testing http://www.testdrivenjavascript.com Test time in javascript - http://googletesting.blogspot.com[..]avascript-simulating-time-in-jsunit.html And this is an example of using JDK6 scripting framework for testing javascript, pretty interesting , but probably not reflecting IE/MOZ behaviour - http://technology.amis.nl/blog/?p=1869 Use a scripting engine to test javascript - http://labnotes.org[..]nsanely-fast-full-stack-headless-testing
(google search)
(amazon search)
Wed Nov 17 00:48:42 HKT 2010
From /weblog/software_engineering/testing
Here is a more complicated framework, not looking good but still keep it here as the concept is interesting - http://sourceforge.net/projects/cubictest The most excellent implementation for my need - http://www.concordion.org/ http://www.jamesshore.com/Blog/Five-Ways-to-Misuse-Fit.html - Don't use it as junit, "The whole point of Fit is to use HTML to speak the customer's language and fixtures to translate that language to code. " http://jroller.com/njain/entry/is_fitnesse_ready_for_enterprise - Version control is #1 issue at that article When use Fit/Fitness - http://madcoderspeak.blogspot.com[..]-do-i-use-for-acceptance-tests-atdd.html
(google search)
(amazon search)
Fri Oct 30 16:42:36 HKT 2009
From /weblog/software_engineering/testing
Yet other discussion of Stubs, Fakes, and Mock Objects - http://vladimirlevin.blogspot.com/2007/11/stubs-fakes-mocks.html While reviewing this article, Marty Andrews pointed out an important insight: there are two ways to use a mock object, either as a testing technique or as a design technique, and the intended use helps shape the available choices. http://www.onjava.com/lpt/a/4526 Someone post some arguement that using mock probably a bad idea , which look like a endless arguement... - http://jroller.com[..]xRuiz?entry=mocks_for_concrete_class_can Alberto Savoia on Testing the Untestable, raise a point that mocking make testing more portable, it probably true, but database setup may be not that difficult to port. - http://www.artima.com/forums/flat.jsp?forum=276&thread=213402 http://gojko.net[..]ut-isolation-but-about-responsibilities/ http://blog.objectmentor.com[..]ing-the-invasion-of-dots-and-parentheses
(google search)
(amazon search)
Mon Apr 06 01:25:04 HKT 2009
From /weblog/software_engineering/testing
This is probably one of the most common question in software testing interview. This problem was first introduced by Myers, who was one of the first person to treat Software Testing as a different subject all together. This test check your ability to think about generating test data in a given condition. Suppose your program accepts input as three sides of a triangle and gives output on what type of triangle is this i.e. Scalene (no sides are same), Isosceles (any two sides are same) or Equilateral (All the three sides are same). You have to come up with different test cases to test this program. You can write your test cases here, by giving side of the triangles and evaluate your test data. Once you are done with all the test cases you can think of, check your performance. If you want to restart your test anytime, just click on the restart test button. I have not covered all the possible test cases here as idea is to give you sufficient information to get started. http://www.testinggeek.com[..]er/154-triangle-test-in-software-testing
(google search)
(amazon search)
|