I agree test code should be of the same high standard as production code. My comment regarding duplication is quite strict. Only allow it if it adds to the story of the test. For example, a method call like userOneLogsIntoTheCashMachine() can be used in each test. This is duplication but it is part of the narrative of the test; without it, the test's behaviour could be hidden in a setup method.

The example above is a little contrived but, until the code you are testing has logic regarding the number of clubs in a bag and valid clubs' lofts, then test data does not need to be real. I would not want to spend too much time setting up real data if it was not required. Obviously for this domain it would not not take long before logic is added so you would need to refactor the test data; thankfully it would only be in one place. A BoundedSequence could be used to generate more realistic data. For example, BoundedSequence.anIntegerSequenceFrom(1, 9) for club number generation.