The only TDD tests I've seen in either project are related to the language specs -- and there the specs were written first.
Agile doesn't simply mean shorter release cycles, although in both articles that's how its used. Iterative waterfall methods result in shorter release cycles.
The key diffs to know the difference: 1) Do you get requirements up-front for a release cycle? The length of the cycle doesn't matter. Can be 1 week or 6 months. 2) Do you have specs for the major features? 3) Do you design up front or do you write tests first? 4) Do you have a big test pass before release?
These are the main diffs in the way waterfall and agile manifests.
Honestly, the only people I know who use Agile are hacks. Every time I've seen anyone try to demonstrate it, it is a disaster. IMO, its the most embarrassing movement in software engineering.