remove failing test, not too useful as an example and then it allows …

…us to set up some automated builds in travis later

contributing.md

@@ -20,4 +20,6 @@ If you don't feel confident to submit your own guide, submitting an issue for so
 
 - Try and minimise the surface area of required knowledge. Thinking of examples that showcase what you're trying to teach without confusing the reader with lots of other features is important.
 - Follow the [Code Review Comments style guide](https://github.com/golang/go/wiki/CodeReviewComments). It's important for a consistent style across all the sections.
+- Your section should have a runnable application at the end (e.g `package main` with a `main` func) so users can see it in action and play with it
+- All tests should pass
 - `go fmt` the code.

for/v1/repeat.go

@@ -1,5 +1,8 @@
 package main
 
-func Repeat(character string) (repeated string)  {
+func Repeat(character string) (repeated string) {
+	for i := 0; i < 5; i++ {
+		repeated = repeated + character
+	}
 	return
-}
+}

for/v2/repeat.go

@@ -1,8 +1,10 @@
 package main
 
+const repeatCount = 5
+
 func Repeat(character string) (repeated string) {
-	for i := 0; i < 5; i++ {
-		repeated = repeated + character
+	for i := 0; i < repeatCount; i++ {
+		repeated += character
 	}
 	return
 }