I see your point @yggie but we don't just write tests for the sake of seeing them pass. Our acceptance test verify that we're building the right thing. E.g. if there is a customer requirement that lesson x should demonstrate the use of the `title` html attribute, and we can test for that then we should.
If the tests are written as well maintained Cucumber then changing them to suit changing requirements will be a conscious decision.
@dcorking and I have started writing such tests for [Workshop 1 content](https://github.com/PeteBoucher/codealia/blob/workshop1/features/workshop1.feature)