nuker 0.0.47 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c9d7ff5ec9e1996f45598d644e6741cda9e55748
-  data.tar.gz: 41fbd7c3764a04c6f0bad4434f1d31568a9bf2f6
+  metadata.gz: 37ddc86185abd564059a00887d9dcc182dce589f
+  data.tar.gz: 57e74e0f863b22e88f2c8a7f3f39a4713ca2b50a
 SHA512:
-  metadata.gz: d1fb0bd6f6a2361a0971ace72e931a5840d2b0d770e1255639c78ec4bbfd52e1728e418dbcf28037b2ba78c2c4098b85f4c2250baa6ed6af985c5d4cb2bc5937
-  data.tar.gz: 884889ec515d576948046e8c68e8869c1f884fb9e4d4d4c6e52d6693c40fffae3b8ac98fae6a904f8624958d6ec735f7fc08eb40c1e556dbb258e1aee2f06c14
+  metadata.gz: 836208fa7c992bb786f868cc026a9e962aae26fce8a20ffc6083f559ebd9c4d070f16262fe980cd0cb3f3f1ab36774ddc446f2cf9202803c3434a9bac608d4d8
+  data.tar.gz: a25d5aa3f191a94b248033fce15a987cc8b0d2487b341cefb90ce0905963d8293cd1ded0157b50845c6ab5661133ea899c1227d48ace9b760860c479c1183c35

data/.gitignore

@@ -0,0 +1,7 @@
+*.swp
+*.gem
+.bundle
+Gemfile.lock
+pkg/*
+.nuker
+chromedriver.log

data/.ruby-version

@@ -0,0 +1 @@
+2.0.0

data/.rvmrc

@@ -0,0 +1,62 @@
+#!/usr/bin/env bash
+
+# This is an RVM Project .rvmrc file, used to automatically load the ruby
+# development environment upon cd'ing into the directory
+
+# First we specify our desired <ruby>[@<gemset>], the @gemset name is optional,
+# Only full ruby name is supported here, for short names use:
+#     echo "rvm use 2.0.0" > .rvmrc
+environment_id="ruby-2.0.0-p481@nuker"
+
+# Uncomment the following lines if you want to verify rvm version per project
+# rvmrc_rvm_version="1.25.28 (stable)" # 1.10.1 seems like a safe start
+# eval "$(echo ${rvm_version}.${rvmrc_rvm_version} | __rvm_awk -F. '{print "[[ "$1*65536+$2*256+$3" -ge "$4*65536+$5*256+$6" ]]"}' )" || {
+#   echo "This .rvmrc file requires at least RVM ${rvmrc_rvm_version}, aborting loading."
+#   return 1
+# }
+
+# First we attempt to load the desired environment directly from the environment
+# file. This is very fast and efficient compared to running through the entire
+# CLI and selector. If you want feedback on which environment was used then
+# insert the word 'use' after --create as this triggers verbose mode.
+if [[ -d "${rvm_path:-$HOME/.rvm}/environments"
+  && -s "${rvm_path:-$HOME/.rvm}/environments/$environment_id" ]]
+then
+  \. "${rvm_path:-$HOME/.rvm}/environments/$environment_id"
+  for __hook in "${rvm_path:-$HOME/.rvm}/hooks/after_use"*
+  do
+    if [[ -f "${__hook}" && -x "${__hook}" && -s "${__hook}" ]]
+    then \. "${__hook}" || true
+    fi
+  done
+  unset __hook
+  if (( ${rvm_use_flag:=1} >= 2 )) # display only when forced
+  then
+    if [[ $- == *i* ]] # check for interactive shells
+    then printf "%b" "Using: $(tput setaf 2 2>/dev/null)$GEM_HOME$(tput sgr0 2>/dev/null)
+" # show the user the ruby and gemset they are using in green
+    else printf "%b" "Using: $GEM_HOME
+" # don't use colors in non-interactive shells
+    fi
+  fi
+else
+  # If the environment file has not yet been created, use the RVM CLI to select.
+  rvm --create  "$environment_id" || {
+    echo "Failed to create RVM environment '${environment_id}'."
+    return 1
+  }
+fi
+
+# If you use bundler, this might be useful to you:
+# if [[ -s Gemfile ]] && {
+#   ! builtin command -v bundle >/dev/null ||
+#   builtin command -v bundle | GREP_OPTIONS="" \grep $rvm_path/bin/bundle >/dev/null
+# }
+# then
+#   printf "%b" "The rubygem 'bundler' is not installed. Installing it now.\n"
+#   gem install bundler
+# fi
+# if [[ -s Gemfile ]] && builtin command -v bundle >/dev/null
+# then
+#   bundle install | GREP_OPTIONS="" \grep -vE '^Using|Your bundle is complete'
+# fi

data/.rvmrc.08.13.2014-14:58:37

@@ -0,0 +1 @@
+rvm 2.0.0@nuker --create --rvmrc

data/.travis.yml

@@ -0,0 +1,3 @@
+rvm:
+  - 2.0.0
+script: bundle exec rspec spec

data/Gemfile

@@ -0,0 +1,4 @@
+source "http://rubygems.org"
+
+# Specify your gem's dependencies in nuker .gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,165 @@
+GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright 2011 British Broadcasting Corporation
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

data/Rakefile

@@ -0,0 +1,5 @@
+require "bundler/gem_tasks"
+
+task :sample do
+  sh "bin/nuker push http://localhost:4567/projects/project1 features/"
+end

data/bin/nuker

@@ -0,0 +1,26 @@
+#!/usr/bin/env ruby
+$:.unshift(File.dirname(__FILE__) + '/../lib') unless $:.include?(File.dirname(__FILE__) + '/../lib')
+
+if ARGV.first == "server"
+  require "nuker"
+  Sinatra::Application.run!
+elsif ARGV[0] == "push"
+  require "restclient"
+  require "json"
+  require "nuker/parses_features"
+  features = []
+  Dir.glob(File.join("#{ARGV[2]}", "**/*.feature")).each do |feature_path|
+    begin
+      gherkin = nuker::ParsesFeatures.new.parse(File.read(feature_path))
+    rescue
+      puts "Couldn't parse '#{feature_path}'"
+      puts "Contents:"
+      puts File.read(feature_path)
+    end
+    features << {:path => feature_path, :gherkin => gherkin}
+  end
+  RestClient.put "#{ARGV[1]}/features/?authentication_code=#{File.read(".nuker").strip}", features.to_json, {:content_type => :json, :accept => :json}
+elsif ARGV[0] == "destroy"
+  require "restclient"
+  RestClient.delete "#{ARGV[1]}?authentication_code=#{File.read(".nuker").strip}"
+end

data/config.ru

@@ -0,0 +1,2 @@
+require './lib/nuker'
+run Sinatra::Application

data/example-features/generic/example-with-background.feature

@@ -0,0 +1,11 @@
+Feature: Feature with a background
+
+  Background:
+    Given I do some stuff
+    And I do some other stuff
+    Then I'm not really sure
+
+  Scenario: Scenario1
+    Given I do this
+    And I do that
+    Then I'm still not sure

data/example-features/generic/example-with-data-table.feature

@@ -0,0 +1,7 @@
+Feature: Data Table
+
+  Scenario: Data Table
+    Given a data table:
+      | a | b | c |
+      | 1 | 2 | 3 |
+      | 4 | 5 | 6 |

data/example-features/generic/example-with-scenario-outline-examples.feature

@@ -0,0 +1,11 @@
+Feature: Scenario Outline
+
+  Scenario Outline: Outline with examples
+    Given there are <start> cucumbers
+    When I eat <eat> cucumbers
+    Then I should have <left> cucumbers
+
+    Examples:
+      | start | eat | left |
+      |  12   |  5  |  7   |
+      |  20   |  5  |  15  |

data/example-features/generic/example_with_tags.feature

@@ -0,0 +1,8 @@
+Feature: Example with tags
+  In order to
+  As a bla
+  I want bla
+
+  @wip
+  Scenario: Do some stuff
+    Given I do some stuff

data/example-features/generic/has-lots-of-tags.feature

@@ -0,0 +1,5 @@
+@batman @robin
+Feature: Has lots of tags
+
+@green_lantern @spider_man
+Scenario: Also has some tags

data/example-features/generic/multiple-scenarios.feature

@@ -0,0 +1,7 @@
+Feature: Multiple Scenarios
+  Scenario: Scenario 1
+  Scenario: Scenario 2
+  Scenario: Scenario 3
+  Scenario: Scenario 4
+  Scenario: Scenario 5
+  Scenario: Scenario 6

data/example-features/too-many-wip-tags/too-many-wip-tags.feature

@@ -0,0 +1,21 @@
+Feature: Too many @wip tags
+  @wip
+  Scenario: Scenario 1
+  @wip
+  Scenario: Scenario 2
+  @wip
+  Scenario: Scenario 3
+  @wip
+  Scenario: Scenario 4
+  @wip
+  Scenario: Scenario 5
+  @wip
+  Scenario: Scenario 6
+  @wip
+  Scenario: Scenario 7
+  @wip
+  Scenario: Scenario 8
+  @wip
+  Scenario: Scenario 9
+  @wip
+  Scenario: Scenario 10

data/features/counts.feature

@@ -0,0 +1,25 @@
+Feature: Counts
+  In order to understand the size of the project
+  As a stakeholder
+  I want a visual indication of the number of tags, scenarios and features
+
+  Background:
+    Given a feature file named "sample.feature" with the contents:
+    """
+    @tag1
+    Feature: Tag Feature
+
+    @tag2 @multiple
+    Scenario: Tag Foo 1
+
+    @tag3 @multiple
+    Scenario: Tag Bar 2
+    """
+
+  Scenario: Features
+    When I visit the project page
+    Then I see "Features (1)"
+
+  Scenario: Tags
+    When I visit the project page
+    Then I see "Tags (5)"

data/features/feature_page.feature

@@ -0,0 +1,69 @@
+Feature: Feature Page
+  In order to view a feature and its intent
+  As a stakeholder
+  I want a page that displays the feature's name, free-form narrative and scenario titles
+
+  Scenario: Content
+    Given a feature file named "sample.feature" with the contents:
+    """
+    Feature: Sample Feature
+      In order to get some value
+      As a person
+      I want to create value
+     """
+    When I visit the sample feature page
+    Then I see the feature free-form narrative
+
+  Scenario: Tags
+    Given a feature file named "sample.feature" with the contents:
+    """
+    @sample_tag
+    Feature: Sample Feature
+    """
+    When I visit the sample feature page
+    Then I see "sample_tag"
+
+ Scenario: Scenario Links
+    Given a feature file named "sample.feature" with the contents:
+    """
+    Feature: Sample Feature
+      In order to get some value
+      As a person
+      I want to create value
+
+    Scenario: Sample Aidy
+      Given my name is "Aidy"
+      When I drink alcohol
+      Then I go nuts
+
+    Scenario: Sample Andrew
+      Given my name is 'Andrew'
+      When I drink alcohol
+      Then I go happy
+     """
+    When I visit the sample feature page
+    Then I see Scenario headers as links
+
+  Scenario: Sort Scenario Links in Alphabetical Order
+    Given a feature file named "sample.feature" with the contents:
+    """
+    Feature: Sample Feature
+      Scenario: V
+      Scenario: C
+      Scenario: I
+      Scenario: N
+    """
+    When I visit the sample feature page
+    Then the scenario links are sorted
+
+  Scenario: Scenario Tags
+    Given a feature file named "sample.feature" with the contents:
+    """
+    Feature: Sample Feature
+
+    @tag1 @tag2
+    Scenario: Sample Aidy
+    """
+    When I visit the sample feature page
+    Then I see "tag1"
+    And I see "tag2"

data/features/list_tags.feature

@@ -0,0 +1,31 @@
+Feature: List Tags
+  In order to be informed of all tags
+  As a stakeholder
+  I want a list of tags to be displayed
+
+  Scenario: Multiple tags
+    Given a feature file named "sample.feature" with the contents:
+    """
+    @tag1
+    Feature: Tag Feature
+    @tag2 @multiple
+    Scenario: Tag Scenario 1
+    @tag3 @multiple
+    Scenario: Tag Scenario 2
+    """
+    When I visit the project page
+    Then I see a link to "@tag1 (1)" with the url "/projects/project/search?q=@tag1"
+    And I see a link to "@tag2 (1)" with the url "/projects/project/search?q=@tag2"
+    And I see a link to "@tag3 (1)" with the url "/projects/project/search?q=@tag3"
+    And I see a link to "@multiple (2)" with the url "/projects/project/search?q=@multiple"
+
+    Scenario: Coloured tags
+      Given a feature file named "sample.feature" with the contents:
+      """
+      @tag1
+      Feature: Tag Feature
+      @tag2 @tag3
+      Scenario: Tag Scenario 1
+      """
+      When I visit the project page
+      Then I see each tag has an individual colour

data/features/notifications.feature

@@ -0,0 +1,9 @@
+Feature: Notifications
+  In order to be great developers
+  As a developer
+  I want to be told off when I have too many bad tags
+
+  Scenario: Ten @wip tags
+    Given a feature file with 10 @wip tags
+    When I visit the project page
+    Then I see a notification that says "You have 10 @wip tags :("

data/features/progress_bar.feature

@@ -0,0 +1,21 @@
+Feature: Progress Bar
+  In order to see the state of the project
+  As a stakeholder
+  I want a visual representation of counted tags
+
+  Scenario: Progress Bar
+    Given a feature file on the project "project_name" with the contents:
+    """
+    Feature: Mixed
+
+    @wip
+    Scenario: WiP
+
+    @notstarted
+    Scenario: Not Started
+    """
+    When I visit the project page for "project_name" 
+    And I select "Progress"
+    Then I see "This project has 2 scenarios"
+    And I see "@wip (50%)"
+    And I see "@notstarted (50%)"

data/features/project_home.feature

@@ -0,0 +1,25 @@
+Feature: Project Home Page
+  In order to simply view a project's complete story set
+  As a stakeholder
+  I want a home page that displays all features
+
+  Scenario: Links to features in alphabetical order
+    Given a feature file named "kate_moss.feature" with the contents:
+    """
+    Feature: Kate Moss
+    """
+    Given a feature file named "katie_price.feature" with the contents:
+    """
+    Feature: Katie Price
+    """
+    Given a feature file named "jessica_jane_clement.feature" with the contents:
+    """
+    Feature: Jessica-Jane Clement
+    """
+    Given a feature file named "elle_macpherson.feature" with the contents:
+    """
+    Feature: Elle Macpherson
+    """
+    When I visit the project page
+    Then I see a link to my sample features
+    And the features are ordered alphabetically

data/features/projects.feature

@@ -0,0 +1,19 @@
+Feature: Projects
+  In order to allow multiple projects
+  As a user
+  I want to be able to switch between projects
+
+  Scenario: Single project
+    Given a feature file on the project "project_name" with the contents:
+    """
+    Feature: Projects
+    """
+    And I visit the project page for "project_name"
+    Then I see a link to the feature "Projects"
+
+  @javascript
+  Scenario: Switch between projects
+    Given 2 projects exist
+    When I view the welcome page
+    Then I can switch to the 2nd project
+    And I can switch to the 1st project

data/features/push_features.feature

@@ -0,0 +1,34 @@
+Feature: Push Features To Server
+  In order to easily get features on the server
+  As a developer
+  I want to be able to push features to an endpoint
+
+  Scenario: Push features without authentication
+    Given I don't have a .nuker authorisation file
+    When I put data to /my_project_name/features with the authentication code
+    Then I get a 403 http status
+
+  Scenario: Push features with authentication
+    Given I have a .nuker authentication file
+    When I put data to /my_project_name/features with the authentication code
+    Then I get a 201 http status
+
+  Scenario: Pushed features show up on home page
+    Given I have a .nuker authentication file
+    When I put data to /my_project_name/features with the authentication code
+    And I visit "my_project_name" page
+    Then I see the uploaded feature
+
+  Scenario: Delete projects without authorisation
+    Given I don't have a .nuker authorisation file
+    And I create a project called "project1"
+    When I send DELETE to "/projects/project1"
+    Then "project1" should exist
+    And I get a 403 http status
+
+  Scenario: Delete projects with authorisation
+    Given I have a .wally authentication file
+    And I create a project called "project1"
+    When I send DELETE to "/projects/project1"
+    Then "project1" should not exist
+    And I get a 201 http status