I don't think extensively testing the view is necessary. Most logic should be kept out of the view so it's not really doing much more than presentation. I also want the view to be flexible and not break any tests when I'm changing the layout.
However, you can't keep all logic out of the view. Sometimes you need to display a certain element in certain conditions. This is something that would be a reasonable test.
The concept of a multilangual site is a good one. In a way it is easier to see what should and should not be tested. The natural language in the view should not be tested because it is too restricting. Something like the wording in the paragraph should be changable without failing tests. If you do need to test whether something is visible or not, use the name/id of an HTML element instead of the natural language inside the element.
That said, the amount of testing is largely dependent upon the project. It's a balancing act between having good test coverage while keeping the flexibility. A good rule of thumb to go by is: if changing something doesn't break the application, but it fails a test, then you have too much test coverage. On the other hand, if you can change something to break the application, and all tests still pass, then you need better test coverage.
- Free Ruby on Rails Screencasts