r-obert 4391aa863e add Pry::Testable, and friends. (#1679) ... * add Pry::Testable, and friends. This commit replaces lib/pry/test/helper.rb by using category modules. There's now: * Pry::Testable: * Pry::Testable::Evalable * Pry::Testable::Mockable * Pry::Testable::Utility * Pry::Testable::PryTester 'include Pry::Testable' includes all of the above. For the pry test suite it worked out best to include 'Pry::Testable' at the top-level. In plugins I've written though this hasn't been the case, and I only normally need: Pry::Testable::Evalable. So it reduces pollution for the third-party cases, which this code is intended for since it lives within lib/ of the project. What do you think? * breaking change: add set_testenv_variables and unset_testenv_variables * breaking change: add Pry::Testable::Variables, and rename constant_scope() to temporary_constants(). * breaking change: rename inject_var as insert_variable, and move its definition to Pry::Testable::Variables. * include Pry::Testable::Evalable & include Pry::Testable::Variables into the top-level, but keep the other two modules spec-local. * document third argument of insert_variable. * update CHANGELOG.md * note changelog entry is a breaking change * update documentation		2017-11-04 05:32:31 +01:00
..
evalable.rb	add Pry::Testable, and friends. (#1679)	2017-11-04 05:32:31 +01:00
mockable.rb	add Pry::Testable, and friends. (#1679)	2017-11-04 05:32:31 +01:00
pry_tester.rb	add Pry::Testable, and friends. (#1679)	2017-11-04 05:32:31 +01:00
utility.rb	add Pry::Testable, and friends. (#1679)	2017-11-04 05:32:31 +01:00
variables.rb	add Pry::Testable, and friends. (#1679)	2017-11-04 05:32:31 +01:00