“If testing costs more than not testing, don’t test.”
~ Kent Beck (via this twitter page)
“Program testing can be used to show the presence of bugs, but never to show their absence.”
~ Edsger Dijkstra
A funny tweet about taking criticism, from this Twitter page.
Problem: How do I use ScalaTest in Eclipse (or, How do I run my ScalaTest unit tests from Eclipse?)
I do a lot of work from the command line with Ant builds and similar things, but there are times I like to do things through Eclipse. Today I wanted to run my ScalaTest unit tests in Eclipse, and found this to be a straightforward task.
Besides Scala, Eclipse, and an Eclipse project, you'll need:
CakePHP/SimpleTest automated web testing: Can you share an example of some automated CakePHP SimpleTest web tests?
Sure, here's a quick look at how I've created a suite of CakePHP automated web tests using SimpleTest to perform integration testing on a new CakePHP web application.
The recipe for creating automated web tests in CakePHP is fairly simple:
CakePHP delete database test data FAQ: How can I delete CakePHP test data from my database in automated CakePHP unit and web tests (integration tests)?
I recently created a large set of CakePHP unit tests and CakePHP web tests (essentially integration tests), and as part of thorough testing, I needed to be able to create some user accounts and insert some test data into the database.
In the category of best practices I have to include my thoughts today on unit tests as a form of "comments/documentation you can compile". Let me explain:
I recently had the experience of (a) working on a small but complicated software development project, (b) leaving that project for six months, and then (c) being asked to work on it again. All I can say it wow -- what a great experience it was to come back to a project that was loaded with unit and code coverage tests.
As I mentioned in a previous blog entry (eXtreme GUI Testing, Part 1) I've been motivated to work on a project in my spare time, and I'd like to start leaking the details here.
For lack of a better name I'm currently calling this project eXtreme GUI Tester, or XGT for short. As its name implies, this is an application (actually a suite of applications) that hopes to make automated GUI testing a little more of a reality.
The grand experiment has begun. The problem: I've been on a project developing a very deep application for four years now, and lately it's become so complex and intertwined that things are starting to break. Developers have been known to say "The application is smarter than I am." I'm just a wee bit concerned about our software quality.
Throughout all of this I started to notice that many of these bugs could be found if we had ... (drumroll) ... automated GUI tests.