Writing a test that checks for static text on a page or dialog that will never change based on domain logic or system behavior and then writing the text to make it pass…
That’s not test driven development. It’s just a complete waste of time and absolutely stupid. By the kind of contrived logic such tests are based on, I should be writing tests for each of my blog posts. 
It depends: if your text is dynamic and selected for this specific page from some kind of repository (map, db, whatever), that could be a useful test to check that the correct page is displayed, and not another one… But yeah, the situation you describes (static text) looks like theoretical-school-like TDD, not a real case. Any real TDDer knows not to waste time on doing EVERYTHING using TDD. Don’t we?
For your blog test, I guess if you write your blog engine using TDD, then you don’t need to test each post (I know it was a joke, but still).