xcfit 0.8.0 → 0.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 359a742c6da8b3f8cac4cb608af043b999a0d770
-  data.tar.gz: ee93c85a6b1ded10dceb6e82ed114b87de5dc988
+  metadata.gz: c0f7f8725d28712acee9f6958cc1614ccecd887c
+  data.tar.gz: 6e222f03ee57c9f98281a8b2842b332ddac0a3dd
 SHA512:
-  metadata.gz: c7b3d8ad162aae77bba2720c1f8b38dc4ccad1529fba03de3ad38162dfad66e76e7f9288a50ff8d02f3dbcb19f904f59d728770ed0f9c1095adbfab047881369
-  data.tar.gz: 18f8a4c526e5dd480c49929280d95dcf1d047b9b2771b71bbf6ba983f4c81dcc1e0d8b596a8b665d6a8f296eff055d5ef96d1d5a0c2c5f43bf336b13a693d93d
+  metadata.gz: 760a8546ee0e8c3d0cb73c4524ebdf408a371e92d321f07a368ad873e8ff46f2c12010b18934df3b727078a6eb8f019ff94eea95d785a9bb5fc1d12179bc8bf0
+  data.tar.gz: 9956a797e7f8c38041f0985e97ba3c9a662ae785e11c31a128c36bad9f78db27beb4a755f880c614e59aeb6b26fac2f992fb954b181ac652d525b0373a485720

data/.travis.yml

@@ -5,10 +5,15 @@
 osx_image: xcode7.3
 language: objective-c
 # cache: cocoapods
-# podfile: Example/Podfile
-# before_install:
-# - gem install cocoapods # Since Travis is not always on latest version
-# - pod install --project-directory=Example
+podfile: XCFitDemo/Podfile
+before_install:
+ - gem install danger
+ - danger
+#  - pod install --project-directory=XCFitDemo
 script:
-- set -o pipefail && xcodebuild test -workspace Example/XCFit.xcworkspace -scheme XCFit-Example -sdk iphonesimulator9.3 ONLY_ACTIVE_ARCH=NO | xcpretty
-- pod lib lint
+ - cd XCFitDemo/
+ - pwd
+ - set -o pipefail && xcodebuild -list
+ - echo "==========Now Running Cucumberish Tests==================="
+ - set -o pipefail && xcodebuild -project XCFitDemo.xcodeproj -scheme XCFitDemo -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6,OS=9.3' clean build test | xcpretty -s -r html -r junit --color
+ 

data/Dangerfile

@@ -0,0 +1,11 @@
+# Sometimes it's a README fix, or something like that - which isn't relevant for
+# including in a project's CHANGELOG for example
+declared_trivial = github.pr_title.include? "#trivial"
+
+# Make it more obvious that a PR is a work in progress and shouldn't be merged yet
+warn("PR is classed as Work in Progress") if github.pr_title.include? "[WIP]"
+
+# Warn when there is a big PR
+warn("Big PR") if git.lines_of_code > 500
+
+

data/README.md

@@ -3,26 +3,71 @@
 [![License](https://img.shields.io/cocoapods/l/XCFit.svg?style=flat)](http://cocoapods.org/pods/XCFit)
 [![Platform](https://img.shields.io/cocoapods/p/XCFit.svg?style=flat)](http://cocoapods.org/pods/XCFit)
 
-# XCFit
+#XCFit
+## XCFit - 'Swift' Your iOS/macOS apps towards BDD
+
+####XCFit a.k.a ([XCUI](https://developer.apple.com/videos/play/wwdc2015/406/0), [Cucumberish](https://github.com/Ahmed-Ali/Cucumberish) and [Fitnesse](https://github.com/paulstringer/OCSlimProject) Integrations Tests) is a full stack Xcode BDD framework for [Swift](https://swift.org) iOS and macOS apps. XCFit allows us to write API, UI and Acceptance Tests with Swift in human readable language using tools like [Cucumber](https://cucumber.io/) and [Fitnesse](http://fitnesse.org/) in Xcode. We can still use Apple's brand new UI Testing framework (XCUI) under the hood of Cucumberish. XCFit is fully automated solution for Cucumberish and Fitnesse. You can use 80(Fitnesse):20(Cucumberish) formula to automate Acceptance and UI Testing for better coverage and faster feedback. XCFit is available on [RubyGem](https://rubygems.org/gems/xcfit) and [CocoaPods](http://cocoadocs.org/docsets/XCFit).
 
-####XCFit a.k.a ([XCUI](https://developer.apple.com/videos/play/wwdc2015/406/0), [Cucumberish](https://github.com/Ahmed-Ali/Cucumberish) and [Fitnesse](https://github.com/paulstringer/OCSlimProject) Integrations Tests) is a full stack Xcode BDD framework for [Swift](https://swift.org) iOS and macOS apps. XCFit allows us to write API, UI and Acceptance Tests in human readable language using tools like [Cucumber](https://cucumber.io/) and [Fitnesse](http://fitnesse.org/) in Xcode. XCFit is fully automated solution for Cucumberish and Fitness. XCFit is available on [RubyGem](https://rubygems.org/gems/xcfit) and [CocoaPods](http://cocoadocs.org/docsets/XCFit).
 
 ### XCFit Features
 There are few reason you should go for XCFit
 ***
   -  You can now write Given When Then and Decision Table in Xcode !! YAY.. Thanks to Cucumberish and OCSlimProject ! And XCFit automated them !!
+  -  You can now write/Execute all your Acdeptance Tests and UI Tests using Apple's brand new programming language "Swift" in Xcode. Goodbye Appium, Calabash, Frank, KIF and Goodbye Ruby,Java, Python. It's pure Swift !!
 
-  -  XCfit provides Xcode Templates to create new Cucumberish and Fitnesse targets which reduce hectic Xcode configuration steps. It's all automated in XCfit
+  -  XCFit provides Xcode Templates to create new Cucumberish and Fitnesse targets which reduce hectic Xcode configuration steps. It's all automated in XCFit
   -  One command to set all fully automated Xcode template for Cucumberish and Fitnesse targets
   - New Template to create Gherkin Feature file in Xcode
-  - Automated almost all [Cucumberish](https://github.com/Ahmed-Ali/Cucumberish) Setup in one command
-  - Enhanced OCSlimProject (https://github.com/paulstringer/OCSlimProject) templates and automated Fitnesse download process.
+  - Automated [Cucumberish](https://github.com/Ahmed-Ali/Cucumberish) Setup in one command
+  - Enhanced [OCSlimProject](https://github.com/paulstringer/OCSlimProject) templates and automated Fitnesse download process.
   - XCFit target templates are independent of native Xcode Test targets.
-  - Its native Xcode implementation, No Appium, Calabash etc etc
+  - We can stiil use Apple's brand new XCUI Testing framework. Its native Xcode implementation, No Appium, Calabash etc etc
   - Setup Cucumberish and Fitnesse in Xcode within few minutes !!
 
   ***
 
+
+### Quick Demo with Example App
+
+You can clone the existing repo which has a demo app. To get started..Watch this animated GIF for the steps below. 
+
+  ![image](https://github.com/Shashikant86/XCFit-GIFS/blob/master/Quick_Demo.gif)
+
+  ```
+  $ git clone https://github.com/Shashikant86/XCFit
+  $ cd XCFit/XCFitDemo
+  $ open XCFitDemo.xcworkspace
+  ```
+  Run Unit, UI and Cucumberish test with Xcode. "cmd + U". Edit Scheme if nessesary to avoid running Unit Tests for this demo. Or Run nit from command line. Update Simulator device/OS version as installed in your Xcode if nessessary
+
+  ```
+  $ xcodebuild -workspace XCFitDemo.xcworkspace -scheme XCFitDemo -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6,OS=9.3' test | xcpretty -r html -r junit --test --color
+```
+  Watch out HTML and JUnit reports generated in the 'Build/reports/' directory with XCPretty. Install XCpretty if you havent got already.
+
+  Running Fitnesse Tests: Clean, Build and Execute
+
+  ```
+  $ xcodebuild -workspace XCFitDemo.xcworkspace -scheme XCFitAcceptanceTests -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6,OS=9.3' clean build | xcpretty
+
+  $java -jar fitnesse-standalone.jar -v -o -c "FrontPage?suite&format=junit"
+
+  ```
+
+###### Using Fastlane
+
+Assuming you have Bundler  rubygem installed if not install it by "gem install bundler"
+
+```
+$ bundle install
+$ bundle exec fastlane cucumberish
+$ bundle exec fastlane fitnesse
+```
+
+
+Curently XCFitDemo App is configured on TravisCI which runs both Cucumberish and Fitnesse Tests. The sample .travis.yml is in the Github repo and sample logs from TravisCI [here](https://travis-ci.org/Shashikant86/XCFit/builds/145963673).
+
+
 Big Thanks to
   - [Cucumberish](https://github.com/Ahmed-Ali/Cucumberish) : Provide native [Gherkin](https://github.com/cucumber/cucumber/wiki/Gherkin) parser for iOS Apps to enable BDD in Xcode using Given When Then. Yay!
   - [OCSlimProject](https://github.com/paulstringer/OCSlimProject) : Provide Xcode Templates to enable BDD with Decision Tables using Fitnesse
@@ -30,9 +75,9 @@ Big Thanks to
 XCFit automated configuration of these two guys.
 
 ### Version
-CocoaPods -- [XCFit-CocoaPods](http://cocoadocs.org/docsets/XCFit) : TBD
+CocoaPods -- [XCFit-CocoaPods](http://cocoadocs.org/docsets/XCFit) : 0.1.0
 
-RubyGems  -- [xcfit-RubyGem](https://rubygems.org/gems/xcfit)  : TBD
+RubyGems  -- [xcfit-RubyGem](https://rubygems.org/gems/xcfit)  : 0.8.0
 
 ### Tech & Software Requirements
 
@@ -45,6 +90,7 @@ Software:
 * [Xcode](https://developer.apple.com/xcode/) - Ideally Xcode 7.X
 * [RubyGems](https://rubygems.org/) - RubyGem with [Cocoapods](https://cocoapods.org/) installed
 * [Curl on Mac](https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/curl.1.html) - Might be pre-installed but worth double checking.
+* Ruby Packages : Xcpretty, Fastlane(Optional), Rake, Bundler.. Install with 'gem install <package_name>'
 
 
 ### Installation
@@ -86,38 +132,61 @@ $ xcfit set_xcode_templates
 
 You will see new option for iOS and OSX i.e 'XCFit'. Once Clicked on it. You will see Cucumberish API, Cucumberish UI and Fitnesse Acceptance Tests targets. As shown
 
+![image](https://github.com/Shashikant86/XCFit-GIFS/blob/master/new_targets.png)
+
 
 
 - Once Clicked on the target e.g 'Cucumberish UI Test Bundle' Xcode will create UI testing target with all the required files with Bridging hrader for Cucumberish UI Testing.
-Once Clicked on the target e.g 'Fitnesse Acceptance Test Bundle' Xcode will create UI tAcceptance test with all the required files with Bridging headers for the Fitnesse Acceptance Test. We will see that in details soon. 
+Once Clicked on the target e.g 'Fitnesse Acceptance Test Bundle' Xcode will create UI tAcceptance test with all the required files with Bridging headers for the Fitnesse Acceptance Test. We will see that in details soon.
 
-- This script also set new file type in Xcode to create new Gherking feature file 
+![image](https://github.com/Shashikant86/XCFit-GIFS/blob/master/XCFit_Setup.gif)
+You can watch YouTube video of XCFit setup [here](https://www.youtube.com/watch?v=Q3cKinwYwhE)
+
+- This script also set new file type in Xcode to create new Gherking feature file
 
 ## Setting up Cucumberish UI Target
 
-3 Steps to setup Cucumberish. You don't need to use Cocoapods to setup this target. 
+3 Steps to setup Cucumberish. You don't need to use Cocoapods to setup this target.
 
 
 - Add new target iOS/macOS project and Select "File -> New -> Target -> XCFit -> Cucumberish UI Test Bundle". Give it a name you like e.g CucumberishUITests
 
-Now that Xcode has created brand new target with all required Swift and Objective-C files to run Cucumberish. All Xcode setting has been done by the Xcode Template. Don't worry about configuting anything. 
+Now that Xcode has created brand new target with all required Swift and Objective-C files to run Cucumberish. All Xcode setting has been done by the Xcode Template. Don't worry about configuting anything.
 
 
 - Now that you have to CD into the Cucumberish target directory .eg CucumberishUITests
 
-```sh 
+```sh
 $ cd $CUCUMBERISH_TARGET_DIR
 $ xcfit get_cucumberish 0.0.7
 ```
 This will download Cucumberish directory from version 0.0.7 and also creats 'Features' directory. You can then reference those directory in Xcode. For "Cucumberish" directory select 'Copy if needed and Create Group' and for the "Features" directory select don't create group or Copy if needed. Just " create folder reference"
+Now Add sample Feature File to 'Features' directory either by File->New->Gherkin Or Just add it using your favourite text editor e.g demo.feature with content 
 
-- Finally from the Cucumberish target 'General' setting select 'Testing -> Target To Test' and configure scheme to add Cucumeerish UI target to Test 
+```
+Feature: Demo App Feature
+
+Scenario: Demo Scenario 
+
+Given the app is running
+
+```
+
+- Finally from the Cucumberish target 'General' setting select 'Testing -> Target To Test' and configure scheme to add Cucumeerish UI target to Test
 
 You are done !!
 
+You can watch YouTube video of Cucumberish Setup [here](https://www.youtube.com/watch?v=Wd9myhNkpx4)
+
+You can add more feature/Scenarios and implement steps definitions inside your Swift File. [Ahmed-Ali](https://github.com/Ahmed-Ali) creator of Cucumberish already implemented useful pre-defined steps have a look at this [Swift file](https://github.com/Ahmed-Ali/Cucumberish/blob/master/CucumberishExample/CucumberishExampleUITests/CCIStepDefinitions.swift). You are free to try Page Object Pattern and all other crazy stuff to abstract and refactor your Swift code. 
+
+
+
+![image](https://github.com/Shashikant86/XCFit-GIFS/blob/master/CucumberishDemo.gif)
+
 ## Setting up Fitnesse Acceptance Target
 
-You can also setup Fitnesse Acceptance Tests but you need to use Cocoapod for this target. 
+You can also setup Fitnesse Acceptance Tests but you need to use Cocoapod for this target.
 
 Basically Steps are pretty much same mentioned in the [OCSlimProject](http://paulstringer.github.io/OCSlimProject/) but most of them are automated for simplicity. Here is simple way to set Fitnesse Acceptance tests for iOS/MacOS Apps
 
@@ -125,7 +194,7 @@ Basically Steps are pretty much same mentioned in the [OCSlimProject](http://pau
 
 - Create new target, "File --> New --> Target --> XCFit --> Fitnesse Acceptance Test". Give it a suitable name e.g 'AcceptanceTests'
 
-- Create/Update Podfile with 
+- Create/Update Podfile with
 
 
 ```ruby
@@ -137,9 +206,9 @@ target 'AcceptanceTests' do
 end
 ```
 
-Run 'Pod install' and build newly created Acceptance target from Xcode. You should see 'LaunchFitnesse' Script geerated and Your app should be talking to fitnesse now. 
+Run 'Pod install' and build newly created Acceptance target from Xcode. You should see 'LaunchFitnesse' Script geerated and Your app should be talking to fitnesse now.
 
-- Now CD into FITNESSE_TARGET directory and Get Fitnesse JAR file by running 
+- Now CD into FITNESSE_TARGET directory and Get Fitnesse JAR file by running
 
 ```sh
 $ cd $FITNESSE_TARGET
@@ -154,51 +223,135 @@ $ ./LaunchFitnesse
 
 Now you should have Fitnesse up and runnig. Follow Paul's article for the details on how to write acceptance tests [here](http://stringerstheory.net/acceptance-testing-with-ios/)
 
-## Continous Integration & Test Reporting 
+You can watch YouTube video of XCFit Fitnesse [here](https://www.youtube.com/watch?v=Wd9myhNkpx4)
+
+![image](https://github.com/Shashikant86/XCFit-GIFS/blob/master/AcceptanceTests.gif)
 
-As of now, you might be running tests within Xcode, but there are some awsome tools which allows us to run our tests from command line. The 'xcodebuild' is being used to build and test Xcode Schemes. [Fastlane](https://github.com/fastlane/fastlane) seems much easier option to automate everything but it's upto you. These are long commands but you k ow better how to Script it Or Fastlane it, right ? :) 
+## Continous Integration & Test Reporting
+
+Continous Integration is very important and you simply can't avoid that. XCFit will be easily configured on any CI server including Apple's own [Xcode Server](https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/xcode_guide-continuous_integration/) or very polular one [Jenkins](https://jenkins.io/) as we can generate reports in both HTML and JUnit format. 
+As of now, you might be running tests within Xcode, but there are some awsome tools which allows us to run our tests from command line. The 'xcodebuild' is being used to build and test Xcode Schemes. [Fastlane](https://github.com/fastlane/fastlane) seems much easier option to automate everything but it's upto you. These are long commands but you k ow better how to Script it Or Fastlane it, right ? :)
+
+Curently XCFitDemo App is configured on TravisCI which runs both Cucumberish and Fitnesse Tests. The sample .travis.yml is in the Github repo and sample logs from TravisCI [here](https://travis-ci.org/Shashikant86/XCFit/builds/145963673). Watch out Live Execution : 
+
+![image](https://github.com/Shashikant86/XCFit-GIFS/blob/master/Travis_XCFit.gif)
 
 ### Cucumberish
- 
-You can execute Cucumberish tests with like this for XCFitDemo App. 
 
-[XCPretty](https://github.com/supermarin/xcpretty) can be used to generate JUnit Or HTML report as below 
+You can execute Cucumberish tests with like this for XCFitDemo App.
+
+[XCPretty](https://github.com/supermarin/xcpretty) can be used to generate JUnit Or HTML report as below
 
 
 ```sh
-xcodebuild -workspace XCFitDemo.xcworkspace -scheme XCFitDemo -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6' test | xcpretty --test --color
+xcodebuild -workspace XCFitDemo.xcworkspace -scheme XCFitDemo -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6' test | xcpretty -r html -r junit --test --color
 ```
 
-You can now analyse the reports generated in the 'build/reports' directory. 
+You can now analyse the reports generated in the 'build/reports' directory. You will find both HTML and JUnit reports. You can configure these reports with Xcode-Server, Jenkins, TeamCity easily in the post build setting. 
+
+```
+$ open build/reports/tests.html
+```
+
+
+![image](https://github.com/Shashikant86/XCFit-GIFS/blob/master/html_reports.png)
 
-### Fitnesse 
+### Fitnesse
 
 You can first build the Acceptance target
 
-```sh 
+```sh
 $ xcodebuild -workspace XCFitDemo.xcworkspace -scheme XCFitAcceptanceTests -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6' clean build | xcpretty
 ```
 
-Now run the Fitnesse tests using 
+Now run the Fitnesse tests using
 
 ```sh
 
 $ java -jar fitnesse-standalone.jar -v -o -c "FrontPage?suite"
 ```
-You can also set reports directory and generate Junit style reports inside the "XCFitDemo/FitNesseRoot/files/testResults/" directory. 
+You can also set reports directory and generate Junit style reports inside the "XCFitDemo/FitNesseRoot/files/testResults/" directory. You can configure these reports with Xcode-Server, Jenkins, TeamCity easily in the post build setting. 
+
+
+
+## What XCFit can solve in iOS/macOS team?
+XCFit can bring lot of improvement the way you work. The most common problems in iOS development is explained by Paul Stringer in this [article](http://stringerstheory.net/acceptance-testing-with-ios/). XCFit can solve few of them
+
+  - Better Developer/QA collabration, Early QA Involvement.
+
+Usually,in the iOS development world, Developer build an app using Swift and Objective-C and army of manual and automated QA uses tools like Apppium, Calabash using languages like Ruby, Java, Python WTF !!. QA and Developers world is totally different. With XCFit you will be speaking same language that is "Swift". QA can write test script as we build. No need to wait until build is handed over. Just work with developer ! Little bit of learning curve for QA but you will save developers time as they don't to learn Java, Pyth or Ruby to help QA team
+
+   - Quick Acceptance & UI testing setup
+
+You will be surprised by how easily/quickly you can setup Fitnesse(Acceptance Test) and Cucumberish(UI Testing) environmant in Xcode and running your first test.
+
+   -  Getting Business people involved
 
+As we can now able to write scenarios with Given/When/Then and decision tables. We can get business people involved to contribute to acceptance criteria. In short we got all benefits of BDD in iOS/macOS project.
 
-# Video Demo 
+   - Developers don't need to learn Ruby or similar ! Just stick to Swift
 
-Coming Soon !
+You must be happy as you won't need to learn other language just in case QA ask something to solve. With XCFit it's everything Swift.
 
+  - Fix failed attempt to automate testing by QA team
 
+As of now your QA team might have tried all wrappers on [UIAutomation](https://developer.apple.com/library/tvos/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/UIAutomation.html) e.g Appium, Calabash, Frank, KIF etc etc and keeping themselve busy writing some Ruby, Python, Java code to automate testing and all that attempts results in Slow, Brittle, Untrusted, Non-valuable UI tests causing harm to mobile development rather than good. With XCFit, everyone will be speaking same language and you can cover businness logic with lighting fast Fitnesse Tests and major journeys with UI tests. Keep it 80:20 means 80% Fitness and 20% Cucumberish or XCUI.
 
 
+
+# Video Demo
+
+### XCFit Xcode Setup
+
+[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/Q3cKinwYwhE/0.jpg)](http://www.youtube.com/watch?v=Q3cKinwYwhE)
+
+
+### XCFit Cucumberish Demo
+
+[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/Wd9myhNkpx4/0.jpg)](http://www.youtube.com/watch?v=Wd9myhNkpx4)
+
+
+### XCFit Fitnesse Demo
+
+[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/xFRSIugJ-FA/0.jpg)](http://www.youtube.com/watch?v=xFRSIugJ-FA)
+
 ## Author
 
 Shashikant86, shashikant.jagtap@icloud.com
 
-## License
+# TODO
+
+ * Swift Implementation of Gherkin Parser 
+ * Cocoapods free installation. Carthage or Swift Package Manager once ready 
+ * Setting up XCFit on Apple's own CI Xcode Server 
+
+## LICENSE
+
+Copyright © 2014 Shashikant Jagtap, http://shashikantjagtap.net
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+## Contributing
 
-XCFit is available under the MIT license. See the LICENSE file for more info.
+1. Fork it ( https://github.com/Shashikant86/XCFit/fork )
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create a new Pull Request

data/XCFitDemo/.travis.yml

@@ -0,0 +1,20 @@
+# references:
+# * http://www.objc.io/issue-6/travis-ci.html
+# * https://github.com/supermarin/xcpretty#usage
+
+osx_image: xcode7.3
+language: objective-c
+# cache: cocoapods
+# podfile: XCFitDemo/Podfile
+before_install:
+ - bundle exec danger
+script:
+ - cd XCFitDemo/
+ - pwd
+ - set -o pipefail && xcodebuild -list
+ - echo "==========Now Running Cucumberish Tests==================="
+ - set -o pipefail && xcodebuild -project XCFitDemo.xcodeproj -scheme XCFitDemo -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6,OS=9.3' clean build test | xcpretty -s -r html -r junit --color
+ - echo "==========Now Building target for Fitnesse ==================="
+ - set -o pipefail && xcodebuild -workspace XCFitDemo.xcworkspace -scheme XCFitAcceptanceTests -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6,OS=9.3' clean build | xcpretty
+ - echo "==========Now Running Fitnesse Tests ==================="
+ - set -o pipefail && java -jar fitnesse-standalone.jar -v -o -c "FrontPage.XCFitDemoFitnesse.XCFitDemoFitnesseSuite?suite&format=junit"

data/XCFitDemo/Dangerfile

@@ -0,0 +1,13 @@
+# Sometimes it's a README fix, or something like that - which isn't relevant for
+# including in a project's CHANGELOG for example
+declared_trivial = github.pr_title.include? "#trivial"
+
+# Make it more obvious that a PR is a work in progress and shouldn't be merged yet
+warn("PR is classed as Work in Progress") if github.pr_title.include? "[WIP]"
+
+# Warn when there is a big PR
+warn("Big PR") if git.lines_of_code > 500
+
+# Don't let testing shortcuts get into master by accident
+fail("fdescribe left in tests") if `grep -r fdescribe specs/`.length > 1
+fail("fit left in tests") if `grep -r "fit specs/ `.length > 1

data/XCFitDemo/FitNesseRoot/FrontPage/XCFitDemoFitnesse/XCFitDemoFitnesseSuite/AddNumbers/content.txt

@@ -0,0 +1,3 @@
+|Add Numbers   |
+|num1|num2|add?|
+|2   |3   |ok   |

data/XCFitDemo/FitNesseRoot/FrontPage/XCFitDemoFitnesse/XCFitDemoFitnesseSuite/AddNumbers/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Edit>true</Edit>
+<Files>true</Files>
+<Help>AddNumbers</Help>
+<Properties>true</Properties>
+<RecentChanges>true</RecentChanges>
+<Refactor>true</Refactor>
+<Search>true</Search>
+<Test>true</Test>
+<Versions>true</Versions>
+<WhereUsed>true</WhereUsed>
+</properties>

data/XCFitDemo/FitNesseRoot/FrontPage/XCFitDemoFitnesse/XCFitDemoFitnesseSuite/ShouldIEat/content.txt

@@ -0,0 +1,3 @@
+|Should I Eat|
+|hungry |eat?|
+|no     |no  |

data/XCFitDemo/FitNesseRoot/FrontPage/XCFitDemoFitnesse/XCFitDemoFitnesseSuite/ShouldIEat/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Edit>true</Edit>
+<Files>true</Files>
+<Help>ShouldIEat</Help>
+<Properties>true</Properties>
+<RecentChanges>true</RecentChanges>
+<Refactor>true</Refactor>
+<Search>true</Search>
+<Test>true</Test>
+<Versions>true</Versions>
+<WhereUsed>true</WhereUsed>
+</properties>