Commit 59c2a8f0 authored by Tonee Young's avatar Tonee Young
Browse files

Start testing with rspec and guard. WIP

parent e0882809
source 'https://rubygems.org'
gem 'net/http'
gem 'eventmachine', '~> 1.2.7'
gem 'faye-websocket'
gem 'guard-rspec'
# gem 'net/http'
gem 'json'
gem 'date'
gem 'pi_piper'
gem 'faye/websocket'
gem 'eventmachine'
gem 'rspec'
# A sample Guardfile
# More info at https://github.com/guard/guard#readme
## Uncomment and set this to only include directories you want to watch
# directories %w(app lib config test spec features) \
# .select{|d| Dir.exists?(d) ? d : UI.warning("Directory #{d} does not exist")}
## Note: if you are using the `directories` clause above and you are not
## watching the project directory ('.'), then you will want to move
## the Guardfile to a watched dir and symlink it back, e.g.
#
# $ mkdir config
# $ mv Guardfile config/
# $ ln -s config/Guardfile .
#
# and, you'll have to watch "config/Guardfile" instead of "Guardfile"
# Note: The cmd option is now required due to the increasing number of ways
# rspec may be run, below are examples of the most common uses.
# * bundler: 'bundle exec rspec'
# * bundler binstubs: 'bin/rspec'
# * spring: 'bin/rspec' (This will use spring if running and you have
# installed the spring binstubs per the docs)
# * zeus: 'zeus rspec' (requires the server to be started separately)
# * 'just' rspec: 'rspec'
guard :rspec, cmd: "bundle exec rspec" do
require "guard/rspec/dsl"
dsl = Guard::RSpec::Dsl.new(self)
# Feel free to open issues for suggestions and improvements
# RSpec files
rspec = dsl.rspec
watch(rspec.spec_helper) { rspec.spec_dir }
watch(rspec.spec_support) { rspec.spec_dir }
watch(rspec.spec_files)
# Ruby files
ruby = dsl.ruby
dsl.watch_spec_files_for(ruby.lib_files)
# Rails files
rails = dsl.rails(view_extensions: %w(erb haml slim))
dsl.watch_spec_files_for(rails.app_files)
dsl.watch_spec_files_for(rails.views)
watch(rails.controllers) do |m|
[
rspec.spec.call("routing/#{m[1]}_routing"),
rspec.spec.call("controllers/#{m[1]}_controller"),
rspec.spec.call("acceptance/#{m[1]}")
]
end
# Rails config changes
watch(rails.spec_helper) { rspec.spec_dir }
watch(rails.routes) { "#{rspec.spec_dir}/routing" }
watch(rails.app_controller) { "#{rspec.spec_dir}/controllers" }
# Capybara features specs
watch(rails.view_dirs) { |m| rspec.spec.call("features/#{m[1]}") }
watch(rails.layouts) { |m| rspec.spec.call("features/#{m[1]}") }
# Turnip features and steps
watch(%r{^spec/acceptance/(.+)\.feature$})
watch(%r{^spec/acceptance/steps/(.+)_steps\.rb$}) do |m|
Dir[File.join("**/#{m[1]}.feature")][0] || "spec/acceptance"
end
end
## Trigger once day crew reaches 300 good ratings for the day & continue lighting once per hour for the remainder of the day ##
# Trigger once day crew reaches 300 good ratings for the day & continue lighting once per hour for the remainder of the day ##
# Zendesk API Documentation on Satisfaction Ratings:
# Zendesk API Documentation on Satisfaction Ratings:
# https://developer.zendesk.com/rest_api/docs/core/satisfaction_ratings
require 'net/http'
require 'json'
require 'date'
require 'pi_piper'
# require 'pi_piper'
# Have to hardcode this file path bc cron can't see the relative path
require '/Users/tyoung/workspace/Pegacorn_Project/.gitignore/pegacorn_secrets.rb'
......
......@@ -69,7 +69,7 @@ class WatchChatWaits
puts "It's currently #{DateTime.now}."
puts "Chat wait time average is #{wait_time_avg} seconds"
puts "\nLight the pegacorn!\n"
light_it_up
# light_it_up
end
......
require 'count_good_ratings'
require 'rspec'
describe GoodRatingsCount do
context '(smoke test) spec can find class' do
it 'GoodRatingsCount' do
expect(GoodRatingsCount.new).not_to be_nil
end
end
# << THIS TEST DOESN'T WORK >>
context '#write_to_log_file:'do
let(:new_rating) { GoodRatingsCount.new }
it 'affects stdout/log file' do
new_rating.fetchratings_writelog_managepi
expect(new_rating.write_to_log_file(http_response)).to \
change(stdout)
end
end
end
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment