minitest-naga 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 1b3e4a565baedd3f2f9ee2bfb7859a53a2c88c42
+  data.tar.gz: 3a9154301910f14ae88700bcba6980cc38c5a8ca
+SHA512:
+  metadata.gz: 1506d4b851601475b496dcdbe65ba6817f7190f94f2d6af2c6e267476c5179afc42626c523fed1f132ed253e2a9d832f310a13576c82edac428f69e935afa721
+  data.tar.gz: 6485f9ed4d283b0143e1420e1addb65f1cb6ff81ff179497096cf9c95418b4cdef2ebe03dff302f8fd333e6fcb9c4756fd7840adbcc0990ad5a5965d1319ccb0

data/.gitignore

@@ -0,0 +1,11 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+/helpers/
+# rspec failure tracking
+.rspec_status

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.4.1
+before_install: gem install bundler -v 1.16.0

data/CHANGELOG.md

@@ -0,0 +1,85 @@
+# Changelog
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
+and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 10-04-2018
+### Added
+- Added ability to unlock item and other achievements
+- Added an extra city
+- Added restriction so that user can only run a certain amount of times each day
+  depending on their level
+
+### Changed
+- Cleaned up the end of the beginning a bit
+
+### Removed
+- Removed starter achievements to only use one
+
+## [0.1.0] - 08-04-2018
+### Added
+- Added ability to unlock a few starter achievements
+
+### Changed
+- Refined adding item to inventory, either desk, backpack or leave it
+
+## [0.1.0] - 07-04-2018
+### Added
+- Added ability to check if user has completed the beginning
+- Added ability to explore a location
+- Added ability to collect loot and add to desk or inventory
+
+### Changed
+- Only shows the beginning if they haven't completed it already
+
+## [0.1.0] - 05-04-2018
+### Added
+- Furthered the beginning
+
+### Changed
+- Refactored the beginning, better use of Highline
+- Changed so separate methods for adding to inventory and to desk
+
+## [0.1.0] - 03-04-2018
+### Added
+- Added output if user levels up
+
+## [0.1.0] - 20-03-2018
+### Added
+- Added ability to add starter item to inventory
+
+### Changed
+- Only runs Naga when option is attached
+
+## [0.1.0] - 07-03-2018
+### Added
+- Added ability to unlock two more achievements
+- Added colorize gem
+
+### Changed
+- Changed output when user has unlocked achievement
+- Refactored Detector and Achievement class
+
+### Removed
+- Removed use of own colorize class
+
+## [0.1.0] - 04-03-2018
+### Added
+- Added authentication and validates credentials
+- Added ability to unlock first achievement
+
+## [0.1.0] - 26-02-2018
+### Added
+- Added test connection to localhost server to get achievements
+
+## [0.1.0] - 25-02-2018
+### Added
+- Added foundations for minitest extension and achievements
+
+## [0.1.0] - 21-02-2018
+### Added
+- Added bundle gem scaffold
+- Added basic code for game

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at wtwang1@sheffield.ac.uk. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in minitest-naga.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,93 @@
+PATH
+  remote: .
+  specs:
+    minitest-naga (0.1.0)
+      colorize
+      highline
+      httparty
+      minitest
+      thor
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (4.2.10)
+      i18n (~> 0.7)
+      minitest (~> 5.1)
+      thread_safe (~> 0.3, >= 0.3.4)
+      tzinfo (~> 1.1)
+    aruba (0.14.3)
+      childprocess (~> 0.8.0)
+      contracts (~> 0.9)
+      cucumber (>= 1.3.19)
+      ffi (~> 1.9.10)
+      rspec-expectations (>= 2.99)
+      thor (~> 0.19)
+    backports (3.11.1)
+    builder (3.2.3)
+    childprocess (0.8.0)
+      ffi (~> 1.0, >= 1.0.11)
+    colorize (0.8.1)
+    concurrent-ruby (1.0.5)
+    contracts (0.16.0)
+    cucumber (3.1.0)
+      builder (>= 2.1.2)
+      cucumber-core (~> 3.1.0)
+      cucumber-expressions (~> 5.0.4)
+      cucumber-wire (~> 0.0.1)
+      diff-lcs (~> 1.3)
+      gherkin (~> 5.0)
+      multi_json (>= 1.7.5, < 2.0)
+      multi_test (>= 0.1.2)
+    cucumber-core (3.1.0)
+      backports (>= 3.8.0)
+      cucumber-tag_expressions (~> 1.1.0)
+      gherkin (>= 5.0.0)
+    cucumber-expressions (5.0.13)
+    cucumber-tag_expressions (1.1.1)
+    cucumber-wire (0.0.1)
+    diff-lcs (1.3)
+    ffi (1.9.21)
+    gherkin (5.0.0)
+    highline (1.7.10)
+    httparty (0.16.0)
+      multi_xml (>= 0.5.2)
+    i18n (0.9.5)
+      concurrent-ruby (~> 1.0)
+    minitest (5.11.3)
+    multi_json (1.13.1)
+    multi_test (0.1.2)
+    multi_xml (0.6.0)
+    rake (10.5.0)
+    rspec (3.7.0)
+      rspec-core (~> 3.7.0)
+      rspec-expectations (~> 3.7.0)
+      rspec-mocks (~> 3.7.0)
+    rspec-core (3.7.1)
+      rspec-support (~> 3.7.0)
+    rspec-expectations (3.7.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.7.0)
+    rspec-mocks (3.7.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.7.0)
+    rspec-support (3.7.1)
+    thor (0.20.0)
+    thread_safe (0.3.6)
+    tzinfo (1.2.5)
+      thread_safe (~> 0.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activesupport (~> 4.2.0)
+  aruba
+  bundler (~> 1.16)
+  cucumber
+  minitest-naga!
+  rake (~> 10.0)
+  rspec (~> 3.0)
+
+BUNDLED WITH
+   1.16.1

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2018 Wen Ting Wang
+
+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.

data/README.md

@@ -0,0 +1,120 @@
+# Minitest::Naga
+
+Welcome! **Minitest::Naga** is a [minitest](https://github.com/seattlerb/minitest "minitest") extension which lets you unlock achievements
+and collect loot when you run your test suite. This is one half of my disseration project which aims to make unit testing a little bit more fun and to help motivate you to do it. The other part which works
+in hand with this Ruby gem is the [Naga web application](https://naga-unit-testing.herokuapp.com/ "Naga's Homepage").
+The web app's main purpose is to manage all the *(hopefully cool)* features of the system as well as the social aspect (e.g. friends and guilds) of Naga.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'minitest-naga'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install minitest-naga
+
+## Usage
+
+Firstly, you must [sign up](https://naga-unit-testing.herokuapp.com/users/sign_up "Naga's Sign Up Page") in order to use the gem. So go ahead and do that. I'll wait here...
+
+Back? Cool.
+
+Given you have this file (adapted from the example provided by minitest's GitHub repo):
+```ruby
+# a_file_with_lots_of_minitests.rb
+require 'minitest/autorun'
+
+class Meme
+  def i_can_has_cheezburger?
+    "OHAI!"
+  end
+
+  def such_wow
+    "such wow"
+  end
+
+  def will_it_blend?
+    "YES!"
+  end
+end
+
+class TestMeme < Minitest::Test
+  def setup
+    @meme = Meme.new
+  end
+
+  def test_that_kitty_can_eat
+    assert_equal "OHAI!", @meme.i_can_has_cheezburger?
+  end
+
+  def test_that_cate_can_eat
+    assert_equal "OHAI!", @meme.i_can_has_cheezburger?
+  end
+
+  def test_that_doggo_can_eat
+    assert_equal "OHAI!", @meme.i_can_has_cheezburger?
+  end
+
+  def test_that_doge_can_eat
+    assert_equal "OHAI!", @meme.i_can_has_cheezburger?
+  end
+
+  def test_that_it_will_blend
+    assert_equal "YES!", @meme.will_it_blend?
+  end
+
+  def test_that_it_will_not_blend
+    refute_match /^no/i, @meme.will_it_blend?
+  end
+
+  def test_such_wow
+    assert_equal "such wow", @meme.such_wow
+  end
+
+  def test_that_will_be_skipped
+    skip "test this later"
+  end
+end
+```
+
+To use Naga, just run your test file with the `--naga` flag:
+
+    $ ruby a_file_with_lots_of_minitests.rb --naga
+
+For first timers, you'll be asked to enter your email and password. If you've signed in before, it'll continue to run with that account unless you sign out (see below). Once you've successfully done that, you'll be taken on a weird adventure. So I hope you have fun!
+
+If you don't want to use Naga when running your test suite, just omit the flag like so:
+
+    $ ruby a_file_with_lots_of_minitests.rb
+
+### To Sign Out
+
+If you want to sign out, simply run:
+
+    $ minitest-naga signout
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/wtwang1/minitest-naga. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Minitest::Naga project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/minitest-naga/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "minitest/naga"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/exe/minitest-naga

@@ -0,0 +1,4 @@
+#!/usr/bin/env ruby
+require 'minitest/naga/cli'
+
+Minitest::Naga::CLI.start

data/helpers/test_helper.rb

@@ -0,0 +1,55 @@
+# bundle exec ruby -I lib:test helpers/test_helper.rb
+# bundle exec ruby -I lib:test helpers/test_helper.rb --naga
+require 'minitest/autorun'
+
+class Meme
+  def i_can_has_cheezburger?
+    "OHAI!"
+  end
+
+  def such_wow
+    "such wow"
+  end
+
+  def will_it_blend?
+    "YES!"
+  end
+end
+
+class TestMeme < Minitest::Test
+  def setup
+    @meme = Meme.new
+  end
+
+  def test_that_kitty_can_eat
+    assert_equal "OHAI!", @meme.i_can_has_cheezburger?
+  end
+
+  def test_that_cate_can_eat
+    assert_equal "OHAI!", @meme.i_can_has_cheezburger?
+  end
+
+  def test_that_doggo_can_eat
+    assert_equal "OHAI!", @meme.i_can_has_cheezburger?
+  end
+
+  def test_that_doge_can_eat
+    assert_equal "OHAI!", @meme.i_can_has_cheezburger?
+  end
+
+  def test_that_it_will_blend
+    assert_equal "YES!", @meme.will_it_blend?
+  end
+
+  def test_that_it_will_not_blend
+    refute_match /^no/i, @meme.will_it_blend?
+  end
+
+  def test_such_wow
+    assert_equal "such wow", @meme.such_wow
+  end
+
+  def test_that_will_be_skipped
+    skip "test this later"
+  end
+end