trackler 2.0.6.15 → 2.0.6.16

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: d2be37cbc31136941811e051179467879b92babc
-  data.tar.gz: 14dfc0634c8eacfb96344447eb05bc63dfaafe3d
+  metadata.gz: 93c7f99da67e82bacb69b2baa1335f4fe2fcc2da
+  data.tar.gz: 789b2e7a4936b344dcefb2dcf594d603889c762f
 SHA512:
-  metadata.gz: f9e6fcb733742f7201eca5aff89b7e19de23e040ff3809a77aff1459483226f59b2bab528e70b862149656512677e018025f367be6233c23dfb2e8769b6f9ed5
-  data.tar.gz: b39e788481896ab1b612425a7922dd249defb2c7b6c30091c15b9deeca895ecfc421372d2023c11bfde097ec4297166b9e5917949774a83697ddba7c8d0ea40c
+  metadata.gz: d558ac9c0cea44feb34714b50a7447eda5c3cc0ff7f3ac6c8e9e357f073117ea060ae7b3867d3be38d2f37903275c5b07196bc1c6870754956c7081bb5a33bb0
+  data.tar.gz: d206b1b48daee6f9d5a178f4c50dadec5874bfbf42a0103671bdae92d5994c2c2d116ba6f0e119d538c2204a1b2ddd0c9f8e459c4d2bc0982bb5d5efb6b7bf0b

data/lib/trackler/version.rb

@@ -1,3 +1,3 @@
 module Trackler
-  VERSION = "2.0.6.15"
+  VERSION = "2.0.6.16"
 end

data/tracks/go/config.json

@@ -145,7 +145,11 @@
     {
       "difficulty": 1,
       "slug": "etl",
-      "topics": []
+      "topics": [
+        "Control-flow (loops)",
+        "Maps",
+        "Transforming"
+      ]
     },
     {
       "difficulty": 1,

data/tracks/go/exercises/clock/clock_test.go

@@ -12,15 +12,20 @@ import (
 // (Clock) Add(minutes int) Clock
 //
 // The Add method should also handle subtraction by accepting negative values.
-// To satisfy the readme requirement about clocks being equal, values of
-// your Clock type need to work with the == operator.
+
+// To satisfy the README requirement about clocks being equal, values of
+// your Clock type need to work with the == operator. This means that if your
+// New function returns a pointer rather than a value, your clocks will
+// probably not work with ==.
+//
+// While the time.Time type in the standard library (https://golang.org/pkg/time/#Time)
+// doesn't necessarily need to be used as a basis for your Clock type, it might
+// help to look at how constructors there (Date and Now) return values rather
+// than pointers. Note also how most time.Time methods have value receivers
+// rather than pointer receivers.
 //
-// It might help to study the time.Time type in the standard library
-// (https://golang.org/pkg/time/#Time) as a model.  See how constructors there
-// (Date and Now) return Time values rather than pointers.  Note also how
-// most time.Time methods have value receivers rather than pointer receivers.
-// For more background on this read
-// https://github.com/golang/go/wiki/CodeReviewComments#receiver-type.
+// For some useful guidelines on when to use a value receiver or a pointer
+// receiver see: https://github.com/golang/go/wiki/CodeReviewComments#receiver-type
 
 const targetTestVersion = 4
 

data/tracks/ruby/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,43 @@
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Version used:
+* Environment name and version (e.g. Chrome 39, node.js 5.4):
+* Operating System and version (desktop or mobile):
+* Link to your project:
+
+## Task List
+
+* [ ] First Task
+* [ ] Second Task
+* [ ] Third Task
+
+## References and Closures
+
+<!--- refernces #000 --->
+<!--- closes #000 --->

data/tracks/ruby/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,36 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Description
+<!--- Describe your changes in detail -->
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Screenshots (if appropriate):
+
+## Types of changes
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+
+## References and Closures
+
+<!--- refernces #000 -->
+<!--- closes #000 -->
+
+## Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] My change requires a change to the documentation.
+- [ ] My change relies on a pending issue/pull request
+- [ ] I have updated the documentation accordingly.
+- [ ] I have read the **CONTRIBUTING** document.
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.

data/tracks/swift/.swiftlint.yml

@@ -1,15 +1,20 @@
-variable_name: 
-    min_length: 
+variable_name:
+    min_length:
         warning: 1
         error: 0
 
+colon:
+  apply_to_dictionaries: false
+
 force_try: warning
 
 opt_in_rules:
   - vertical_whitespace
-    
+  - closure_spacing
+
 disabled_rules: # rule identifiers to exclude from running
   - function_body_length
   - line_length
+  - trailing_comma
 
 reporter: "json"

data/tracks/swift/.travis.yml

@@ -1,21 +1,30 @@
-language: objective-c
-osx_image: xcode8
-xcode_project: 'xcodeProject/xSwift.xcodeproj'
-xcode_scheme: 'xSwiftTests'
+language: generic
 
 before_install:
-  - gem install danger xcpretty xcpretty-json-formatter
-  - brew update
-  - brew outdated swiftlint || brew upgrade swiftlint
-
-script:
-  - bin/fetch-configlet
-  - bin/configlet .
-  - swiftlint lint --quiet >> lintreport.json
-  - xcodebuild test -project 'xcodeProject/xSwift.xcodeproj' -scheme 'xSwiftTests' | xcpretty -f `xcpretty-json-formatter`
+    - if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then gem install danger ; fi
+    - if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then brew update ; fi
+    - if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then brew outdated swiftlint || brew upgrade swiftlint ; fi
+    
+matrix:
+  include:
+    - script: 
+        - swiftlint lint --quiet >> lintreport.json
+        - ls
+        - ./xswift-test-spm
+      env: JOB=SPM
+      os: osx
+      osx_image: xcode8.2
+    - script:
+        - bin/fetch-configlet
+        - bin/configlet .
+        - docker run -v `pwd`:/xswift norionomura/sourcekit:302 bash -c "cd /xswift && ./xswift-test-spm"
+      env: JOB=Linux
+      sudo: required
+      services: docker
 
 after_success:
-  - danger
-  - ls -al
-  - python -m json.tool lintreport.json
-  - python -m json.tool build/reports/errors.json
+    - if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then danger  ; fi
+    - if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then ls -al   ; fi
+
+
+

data/tracks/swift/Dangerfile

@@ -42,10 +42,3 @@ json.each do |object|
    	message(msg, file: shortFile, line: line)
    end
 end
-
-# Reports when the test passed
-jsonpath2 = "build/reports/errors.json"
-contents2 = File.read jsonpath2
-json2 = JSON.parse contents2
-firstStrinInArray = json2["tests_summary_messages"][0]
-message(firstStrinInArray)

data/tracks/swift/Package.swift

@@ -0,0 +1,26 @@
+import PackageDescription
+import Foundation
+
+let path = FileManager.default.currentDirectoryPath + "/config.json"
+var allProblems = [String]()
+
+if
+    let jsonData = try? Data(contentsOf: URL(fileURLWithPath: path), options: Data.ReadingOptions.mappedIfSafe) ,
+    let json = try? JSONSerialization.jsonObject(with: jsonData, options: [])  ,
+    let jsonDict = json as? [String: Any],
+    let exercisesDict = jsonDict["exercises"] as? [[String:Any]],
+    let exercises = exercisesDict.map({$0["slug"]}) as? [String],
+    let deprecated = jsonDict["deprecated"] as? [String] {
+
+    allProblems += exercises
+    allProblems += deprecated
+} else {
+    print("Could not parse config.json at \(path)")
+}
+
+let dependencies = allProblems.map { Package.Dependency.Package(url: "./exercises/\($0)/", majorVersion: 1) }
+
+let package = Package(
+    name: "xswift",
+    dependencies: dependencies
+    )

data/tracks/swift/README.md

@@ -8,7 +8,7 @@ Please see the [contributing guide](https://github.com/exercism/x-api/blob/maste
 
 ## Swift Track
 
-We use Travis CI to automatically run all the unit tests on the code that is going to be checked in. In addition we also have [SwiftLint](https://github.com/realm/SwiftLint) set up to make sure that the code is consistent across all exercises. Please run `swiftlint autocorrect --format` on your code before submitting a PR. Also in order for the tests to run they need to be added to the `xcodeProject` project. Make sure all the tests pass locally and that you are using the latest Xcode version otherwise the Travis checks may fail. 
+We use Travis CI to automatically run all the unit tests on the code that is going to be checked in. In addition we also have [SwiftLint](https://github.com/realm/SwiftLint) set up to make sure that the code is consistent across all exercises. Please run `swiftlint autocorrect --format` on your code before submitting a PR. Check the travis file to see which version of swift we are testing against. Make sure all the tests pass locally using the swift package manager. Keep in mind that we support Linux so the tests need to also pass on linux on Travis. 
 
 ## License
 

data/tracks/swift/docs/ABOUT.md

@@ -1 +1,9 @@
-"Swift is an alternative for the Objective-C language that employs contemporary programming language theory concepts and strives to present a simpler syntax. Swift introduces true named parameters and retains key Objective-C concepts, including protocols, closures and categories, often replacing former syntax with cleaner versions and allowing these concepts to be applied to other language structures, like enums." -  https://en.wikipedia.org/wiki/Swift_(programming_language)
+Swift is a modern open source programming language that runs primarily on macOS and Linux. Swift was developed initially by Apple to interoperate with their key frameworks, Cocoa and CocoaTouch, both of which are mostly implemented in Objective-C.
+
+Swift is influenced by a large number of existing programming languages, and it incorporates concepts from a wide range of programming methods, everything from scripting to object oriented and functional programming. Apple refers to Swift as a protocol oriented programming language and has expressed the goal of eventually making Swift useful for everything from scripts to an operating system.
+
+This [Swift Tour](https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.html) is an introduction the language.
+
+A [deeper overview](https://en.wikipedia.org/wiki/Swift_(programming_language)) of Swift from Wikipedia.
+
+Swift is documented in [The Swift Programming Language](https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/index.html) and in the [iBooks Store](https://itunes.apple.com/us/book/swift-programming-language/id881256329?mt=11). The ePub is also available on  [Swift.org](https://swift.org/documentation/#the-swift-programming-language).

data/tracks/swift/docs/INSTALLATION.md

@@ -1,9 +1,17 @@
 ## Installing Swift
 
-In order to use Swift, you must be running Xcode version 8.0 or greater. 
+### macOS
+
+In order to use the Swift exercises, install Xcode version 8.0 or greater. On the first launch of Xcode, install the command line tools when prompted.
 
 The current release version is available at the [Mac App Store](https://itunes.apple.com/us/app/xcode/id497799835?mt=12). 
 
 Additional versions of Xcode (including the most recent beta) are available at [Apple's developer center](https://developer.apple.com/xcode/downloads/).
 
-All exercises tested with Xcode 8.0 using Swift 3
+All exercises have been tested with Xcode 8.0 using Swift 3.
+
+### Linux
+
+The latest release is available on [Swift.org](https://swift.org/download/#releases).
+
+Swift.org installation [instructions](https://swift.org/getting-started/#installing-swift).

data/tracks/swift/docs/TESTS.md

@@ -1,120 +1,85 @@
-## Xcode Tutorial
+## Testing Tutorial
 
-This guide explains how to create and configure a Swift-based Xcode project for Exercism.
+This guide explains how to run unit tests for the Exercism Swift exercises using either macOS or Linux.
 
-Apple does not support user-defined project templates in Xcode, and the default templates are more elaborate than those needed for Exercism. This guide bridges that gap.
-
-These instructions are written with the expectation that some readers will be very new to Xcode. Therefore each step is described in excruciating detail. However, after a few projects, setting up a fresh project should only take a minute.
-
-_As far as housekeeping chores go, you are closer to the finish line than it appears._
+### For experienced users:
+	1. `swift test` runs tests
+	2. `swift package generate-xcodeproj` creates an Xcode project
+	
+To run the tests from the command line, first `cd` to the directory for an exercise (for example, ~/exercism/swift/exercises/hello-world/), then execute `swift test`. This will compile the files in the Sources directory and execute the tests in the Tests directory. Alternatively, open the Xcode project and press Command-U.
 
 ### Overview
 
-To complete an Exercism exercise, you will work primarily with three files:
-
-* **Swift Source** (HelloWorld.swift). This is the file you will create to hold your source code and it is the file you will submit to Exercism.
-* **Test Source** (HelloWorldTest.swift). This file is provided by Exercism. It contains the XCTestCase subclass that defines the solution to the exercise. You never edit this file, but you will have to understand it in order to fulfill its expectations. This is also the file where you will trigger the tests and interpret the results.
-* **Playground** (MyPlayground.playground) is a scratchpad for drafting code snippets and playing with ideas. The code executes as you type, providing instant feedback.
-
-When you reach the end of this tutorial, the file inspector in Xcode will look like this.
-
-![tests_011-finalLayoutExample](/docs/img/tests_011-finalLayoutExample.png)
-
-### Create A New Xcode Project
+The following instructions are written with the expectation that some readers will be very new to test driven development, Exercism, or Xcode. Each step is described in detail.
 
-![tests_001-splash](/docs/img/tests_001-splash.png)
+**macOS users are encouraged to use Xcode.** The Xcode environment provides detailed error messages compared to those available from the command line.
 
-1. Choose the second item in the list shown above to create a new project, or press Command-Shift-N.
-2. Select macOS from the row of buttons at the top of the dialog, then choose the Cocoa Application icon as shown in this image:
+Exercism uses the [Swift Package Manager](https://github.com/apple/swift-package-manager/tree/master/Documentation) to package files and tests for Swift. Packages provide a complete set of source files that can be compiled and executed from the command line.
 
-![tests_002-templatechooser](/docs/img/tests_002-templateChooser.png)
+To complete an Exercism exercise, you will work primarily with two files:
 
-#### Name The Project
-![tests_003-nameproject](/docs/img/tests_003-nameProject.jpg)
+* **Swift Source** (hello-world/Sources/HelloWorld.swift). This is the code file you will submit to Exercism.
+* **Test Source** (hello-world/Tests/HelloWorldTests/HelloWorldTest.swift). This file is provided by Exercism which contains the XCTestCase subclass that defines the solution to the exercise. You never edit this file, but you will have to understand it in order to fulfill its expectations.
 
-1. Enter `HelloWorld` as the Product Name for the project. Spaces and some punctuation symbols are acceptable, but it is better to avoid them early on. _For other exercises, replace the string `HelloWorld` with the exercise name._
-2. Fill in the Organization Name and Bundle Identifier. The Organization Name field will appear in each source file you create. The Bundle Identifier is not used in this context but should not be left blank.
-3. The Language popup should be Swift, the Include Unit Tests checkbox should be selected. All other checkboxes should be deselected.
+Optionally, Xcode can create a third file for experimentation:
 
-#### Save The Project
-![tests_004-saveproject](/docs/img/tests_004-saveProject.jpg)
-
-1. Choose a location to save the project. Anywhere is fine, but a good choice is inside the root folder of the current exercise.
-2. In this example, the Exercism CLI fetched an exercise into a newly created root folder named `hello-world`. The fetched contents include a readme file `README.md` and a Test Source file `HelloWorldTest.swift`. 
-3. Create your project as shown in the above image, inside the root folder `hello-world`. 
-4. The contents displayed inside the Xcode File Inspector do not match the arrangement of the files on the disk. This is confusing at first, but it makes sense as projects become more complex. You will need a general idea of how the layout is different in order to import files later in this tutorial. If you switch to the Finder to explore the file hierarchy now, the files on disk should look like the image below. Essentially Xcode added a new project folder named `HelloWorld` (highlighted) to the root folder `hello-world`.
-
-![tests_005-folderlayout](/docs/img/tests_005-folderLayout.png)
-
-#### Configure the Initial Files in the Project
-
-At this point the project's file inspector should look similar to the image on the left. If the `HelloWorldTests` folder is closed, click on the disclosure triangle to reveal its contents. Many of these files are not needed, so let's move them out of the way.
-
-![tests_006-newprojectinitial](/docs/img/tests_006-newProjectInitial.jpg)
+* **Playground** (MyPlayground.playground) is a scratchpad for drafting code snippets and playing with ideas. The code executes as you type, providing instant feedback.
 
-1. Create a new group folder 'Support' inside the main group then drag the unused files into it. As with many tasks in Xcode, there is a shortcut. In this case you could also Command-Click to select all the unneeded files, and choose `File -> New -> Group from Selection` from the contextual menu.
-2. Look at the image above on the right, note the file `HelloWorldTests.swift`. This file was provided by Xcode. Because Exercism supplies its own test file - often with a similar name - the default Xcode file is unnecessary and should be deleted. To delete the file, select it in the File Inspector and press the Delete key. In the confirmation dialog that appears, move the file to the trash.
-3. Next, create a new playground document. First, make sure to select the topmost item in the File Inspector, the item marked with a blue icon that represents the project file.
-4. Xcode provides several different options to create a new playground, including one called New Playground. However, in order for this step to work properly follow this exactly: press Command-N and choose Playground from the template chooser. Click Next, and click Create.
 
-At this stage, the File Inspector should appear like this:
+### Configuring Xcode
+1. `cd` to the directory for an exercise (for example, ~/exercism/swift/exercises/hello-world/), then execute `swift package generate-xcodeproj` in the Terminal. This creates an Xcode project in the current directory with the same name as the package. (The generated project file is ideal for unit tests, as it does not include overhead such as launching the iOS simulator or a target application.)
+2. Open the newly generated project file.
+3. At this point the project's file inspector should look similar to the following image. If the `HelloWorldTests` folder is closed, click on the disclosure triangle to reveal its contents.
+4. The items Package.swift, Configs, and Products are boilerplate that do not need modification.
 
-![tests_007-fileInspectorUpdate](/docs/img/tests_007-fileInspectorUpdate.png)
+![file inspector](img/file-inspector.png)
 
-#### Make A New Swift Source File For Your Code
+### Running Tests with Xcode
 
-![tests_008-templateChooserSwift](/docs/img/tests_008-templateChooserSwift.png)
+Select the test file from the file inspector. You can trigger tests by clicking on one of the diamonds in the gutter of the Tests Source file. The diamond next to the class definition will run all the tests, whereas the diamond next to each individual test will run only that test.
 
-1. Press Command-N to open the template chooser. Select macOS the Swift File icon, as shown above. 
-2. Near the bottom of the Save As dialog that appears next, set the Group to `HelloWorld` and select only `HelloWorld` from the Targets list.
-3. The filename is up to you and can be changed later. The project name, `HelloWorld`, is a good first choice. By convention Swift classes and structs begin with a capital letter, so their source files should as well.
-4. Click Create. **Note this is the file you will submit to the Exercism web site for review.**
+![tests](img/tests.png)
 
-*Xcode note: If the file appeared in the wrong place, drag it into its preferred position.*
+Tests can also be invoked with Command-U, from the Test Inspector (Command-5), or from the sub-menu under the play button in the top bar. Red errors are normal at this stage.
 
-#### Import The Exercism Test Source File
+![failing tests](img/tests-fail.png)
 
-In the Finder, locate the root folder `hello-world` for this exercise. Drag the file `HelloWorldTest.swift` into the File Inspector so that it inserts into the `HelloWorldTests` group. When the import dialog appears, it should be set up like this:
+Once all the tests are marked with a green icon, congratulations, you have successfully completed the exercise! Now submit it to the Exercism website for review. If you are impossibly stuck, submit the exercise before it is complete to view how other users solved the exercise.
 
-![tests_009-importTestSource](/docs/img/tests_009-importTestSource.png)
+![passing tests](img/tests-pass.png)
 
-Select the newly imported file in the File Inspector to open the source code. Add the line `@testable import HelloWorld` above the class declaration. (When the Xcode project name contains a hyphen, replace it with an underscore. For example, `Word-Count` would become `Word_Count`.) The image below shows how the document should appear. Red errors are likely at this stage, and normal.
+*The Hello-World exercise is a very simple coding problem, but the complexity of Xcode can make even simple exercises complex. We can ignore most of this complexity, because we only need to edit one file. You can always regenerate the Xcode project if something goes wrong.*
 
-![tests_010-testsImportExample](/docs/img/tests_010-testsImportExample.png)
+### Xcode Playgrounds
 
-Here is how the file inspector should look now:
+Playgrounds can be useful for brainstorming solutions to the problem. The playground continuously evaluates code as you type, displaying variable states and results as you type.
 
-![011-finallayoutexample](/docs/img/tests_011-finalLayoutExample.png)
+If you generated an Xcode project, follow these steps:
 
-The housekeeping is finished and Xcode is ready! To review:
+1. First, make sure to select the topmost item in the File Inspector, the item marked with a blue icon that represents the project file.
+2. Press Command-N and choose Playground from the template chooser. Click Next, and click Create.
 
-* **HelloWorld.swift** is the Swift Source code file where you code the solution and later submit it to Exercism.
-* **HelloWorldTest.swift** is the Test Source code file provided by Exercism. It contains the tests that define the exercise.
-* **MyPlayground.playground** is for drafting code snippets and playing with ideas.
+Keep in mind that while playgrounds are useful for drafting code snippets and ideas, code must be moved to the Swift Source file for testing and submission.
 
 ### How Tests Are Used
 
-Test driven development is a very iterative process. The first step is to successfully run the tests (see the next section), and have them fail. Remember that the exercise can be solved with code in the application source file alone. Enter your solution into the Swift Source file. As you type, Xcode will continuously update the display with errors that highlight code that will not compile.
-
-One approach begins with creating a method that returns a correct hard coded value to at least the first test in order for the project to compile. This should confirm that Xcode is passing values between the code and tests properly. Next, create code that generates the expected return value and test again. Keep repeating this basic cycle until all the tests pass.
-
-#### Running The Tests
-
-Trigger a test by clicking on one of the diamonds in the gutter of the Tests Source file. The diamond next to the class definition will run all the tests, whereas the diamond next to each individual test will run only that test.
-
-Tests can also be invoked with Command-U, or from the Test Inspector (Command-5).
+Test driven development is a very iterative process. The first step is to successfully run the tests and have them fail. Remember that the exercise can be solved with code in the application source file alone. Enter your solution into the Swift Source file. Xcode will continuously update the display with errors that highlight code that will not compile.
 
-Once all the tests are marked with a green icon, congratulations, you have successfully completed the exercise! Now submit it to the Exercism website for review. If you are impossibly stuck, submit the exercise before it is complete to view how other users solved the exercise.
-
-*The Hello-World exercise is a very simple coding problem, but the complexity of Xcode can make even simple exercises challenging. If creating a working solution is problematic, the issue may be with how the project is configured. Consider submitting the unfinished exercise to obtain a solution. Then try repeating this tutorial from the beginning with a fresh Xcode project.*
+One approach begins with "sliming a test" by creating a method that returns a correct hard coded value. Sliming will confirm the project can compile and pass one test. Next, replace the hard coded value with code that generates the expected return value and test again. Keep repeating this cycle until all the tests pass.
 
-### Submission
+## Submission
 
 1. In the Terminal, navigate to the folder that contains the application source file. In this example, the path would be `~/exercism/swift/hello-world/HelloWorld/HelloWorld/`
 2. To submit, type `exercism submit HelloWorld.swift` (_Alternatively, you can submit by using the file name with the full path from any directory. A second alternative is to locate the file you need to submit in the Finder. Open the Terminal, type exercism submit followed by a space, then drag the file from the Finder into the Terminal and press return._)
 3. Once uploaded, a URL will appear that reveals your solution on the Exercism web site.
 4. The Exercism CLI allows files to be submitted more than once, and each successive iteration will be added alongside the original.
 
+To review:
+
+* **HelloWorld.swift** is the Swift Source code file where you code the solution and later submit it to Exercism.
+* **HelloWorldTest.swift** is the Test Source code file provided by Exercism. It contains the tests that define the exercise.
+* **MyPlayground.playground** is for drafting code snippets and playing with ideas.
+
 ### Participate in Code Reviews
 
 After you submit a file, follow the URL presented to show the submission on the web. Bookmark it for future reference. From your submission page you can view how others solved the same problem.
@@ -123,7 +88,7 @@ After you submit a file, follow the URL presented to show the submission on the
 
 XCTestCase is the XCTest subclass that contains the test's methods and XCTAssert lines are the expected results. The results are different types depending on how the test is designed.
 
-There is a lot more to learn more about Test Driven Development, XCTAssert Methods and XCTestCase. Unfortunately up-to-date Swift documentation on these topics is short-lived. Although out of date as of when this tutorial was last updated, this curated list of sources contains useful information:
+There is a lot more to learn more about Test Driven Development, XCTAssert Methods and XCTestCase. Unfortunately up-to-date Swift documentation on these topics is short-lived. Although out of date as of when this tutorial was last updated, this list of sources contains useful information:
 
 [Apple's Guide on XCTest](https://developer.apple.com/library/tvos/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/02-quick_start.html#//apple_ref/doc/uid/TP40014132-CH2-SW1)