README.md in doppelserver-0.2.6 vs README.md in doppelserver-0.2.7
- old
+ new
@@ -2,10 +2,11 @@
[](https://travis-ci.org/drewcoo/doppelserver)
[](https://circleci.com/gh/drewcoo/doppelserver)
[](https://coveralls.io/github/drewcoo/doppelserver?branch=master)
[](https://badge.fury.io/rb/doppelserver)
+[](https://www.codacy.com/app/drewcoo/doppelserver?utm_source=github.com&utm_medium=referral&utm_content=drewcoo/doppelserver&utm_campaign=Badge_Grade)
Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/doppelserver`. To experiment with that code, run `bin/console` for an interactive prompt.
TODO: Delete this and the text above, and describe your gem
@@ -35,10 +36,25 @@
$ gem install doppelserver
## Usage
-TODO: Write usage instructions here
+Scenarios this should cover:
+* Fake a server from your (integration) tests
+ * Default behaviors
+ * Imagine a really stupid CRUD database backing the test server,
+ one that auto-created schema as it went. That's pretty much it.
+ How? Easy. Instead of a db it's just a hash in memory. Dumb? Yup.
+ * Overrides
+ * Control endpoints
+* Run interactively (irb/pry console?) while debugging your code
+* Record endpoint usage?
+* Types of service:
+ * REST-ish
+ * GraphQL
+ * Others? (WSDL?)
+* Client bindings? Not sure that makes sense unless it's POROs or x-language.
+
## 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.