googlemock - Google Code
http://code.google.com/p/googlemock/

Google C++ Mocking Framework (or Google Mock for short) is a library for writing and using C++ mock classes.

Google C++ Mocking Framework

Continuous Deployment isn’t just an abstract theory. At IMVU it’s a core part of our culture to ship. It’s also not a new technique here, we’ve been practicing continuous deployment for years; far longer than I’ve been a member of this startup.

unknown terms: tdd, rsync, symlink, schema learned new defn: integrate need to learn big o notat... later. need to sleep

"On average we deploy new code fifty times a day. So what magic happens in our test suite that allows us to skip having a manual Quality Assurance step in our deploy process? The magic is in the scope, scale and thoroughness. It’s a thousand test files and counting. 4.4 machine hours of automated tests to be exact. "

Might be interesting

Article about TDD methodology and practices.

Critical discussion about unit tests. It's important not to dismiss his core argument, that unit testing isn't the only testing you should be doing.

Don't feel bad, it's okay not to write unit tests. But Unit Tests Work For Me! First, are you sure you're really unit testing? Unit testing is all about testing unitsindependent pieces of logic. According to Michael Feathers, a real unit test cannot

There are a variety of C unit testing frameworks available however many of them are fairly complex and require the latest compiler technology. Some development requires the use of old compilers which makes it difficult to use some unit testing frameworks. In addition many unit testing frameworks assume the code being tested is an application or module that is targeted to the same platform that will ultimately execute the test. Because of this assumption many frameworks require the inclusion of standard C library headers in the code module being tested which may collide with the custom or incomplete implementation of the C library utilized by the code under test.

A lightweight library to simplify and generalize the process of writing unit tests for C applications.

A nice unit testing framework for C.

"A lightweight library to simplify and generalize the process of writing unit tests for C applications." Seems simple and uncomplicated.

There are a variety of C unit testing frameworks available however many of them are fairly complex and require the latest compiler technology. Some development requires the use of old compilers which makes it difficult to use some unit testing frameworks. In addition many unit testing frameworks assume the code being tested is an application or module that is targeted to the same platform that will ultimately execute the test. Because of this assumption many frameworks require the inclusion of standard C library headers in the code module being tested which may collide with the custom or incomplete implementation of the C library utilized by the code under test. Cmockery only requires a test application is linked with the standard C library which minimizes conflicts with standard C library headers. Also, Cmockery tries to avoid the use of some of the newer features of C compilers.

How to unit test NHibernate code using an in memory SQL Lite database.

: base(typeof(Blog).Assembly)

Unit Testing NHibernate from Ayende

JS UnitTest Mockup

Second Aspect: While using mockito in Java after many years of being a passionate EasyMock advocate, I have learned that Mockito's way to handle verification of calls after the fact - instead of specifying expectations before - suits my style of test-driven development best. Thus, strictly speaking MockMe should be more of a spying framework than a mocking framework.

There are a couple of mock frameworks for JavaScript but none really did what I needed. So I took my testing problems, some inspiration from mockito and a few days off to write MockMe.

Think Mockito for Javascript

JUnit Integration Test Runner

Ambiente com spring, jetty e banco inmemory em um só classloader para testes. Um espetáculo!

"Essentially, it is in your best interest, as a developer, as a team, to encourage lots and lots of tests lower in the stacks shown here. It starts with comprehensive, checked in unit tests. It continues with having a strong, repeatable testing discipline (for which I recommend test automation)."

As a long-time automation-engineer/test-focused guy I've pondered the great existential question of "how much testing" is enough for awhile. More recently, I've started focusing on the cost of not testing a product.

a great pragmatic look at the value of unit tests in context of total time allocated to project, risk management, acceptance and functional testing. some common issues with unit testing illuminated. a great read.