https://github.com/endeepak/stub_on_web
Create stub urls to test external API integration
https://github.com/endeepak/stub_on_web
api elixir phoenix stub
Last synced: 7 months ago
JSON representation
Create stub urls to test external API integration
- Host: GitHub
- URL: https://github.com/endeepak/stub_on_web
- Owner: endeepak
- License: mit
- Created: 2015-10-22T14:31:45.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2016-01-05T18:07:23.000Z (almost 10 years ago)
- Last Synced: 2023-03-11T08:27:53.345Z (over 2 years ago)
- Topics: api, elixir, phoenix, stub
- Language: Elixir
- Homepage: http://stubonweb.herokuapp.com/
- Size: 0 Bytes
- Stars: 54
- Watchers: 2
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# StubOnWeb [](https://travis-ci.org/endeepak/stub_on_web)
Create stub urls to test external API integration
Try it on http://stubonweb.herokuapp.com
## Running
* Install elixir, mongodb
* To start your app:
mix deps.get
mix ecto.create && mix ecto.migrate
mix phoenix.server
* Now you can visit [`localhost:4000`](http://localhost:4000) from your browser.
* Ready to run in production? Please [check phoenix deployment guides](http://www.phoenixframework.org/docs/deployment).
## Contributing
You can raise issues and feature requests on [github](https://github.com/endeepak/stub_on_web/issues)
If you can code, please fork the repo and raise a pull request
## Alternatives
* http://www.mocky.io/
* https://www.mockable.io/
## Why yet another stub?
StubOnWeb is built to ease the manual testing of multiple scenarios of our service integration with other system's API. The existing web solutions suffer from one or more of the problems listed below
* Doesn't allow to choose your own path for url so it is easy to remember
* Doesn't allow to edit the response. Only way to test multiple scenarios is to create new url and update your app config and restart your services. Oh.. too much work!
* Change requests for new features take longer time. Their tech stack was new and less fun for me to learn & contribute
* Doesn't allow to inspect last few requests for the url
* Over engineered UI / work-flow for the job
And I was learning [elixir](http://elixir-lang.org/). This was simple enough and fun to try out!
## Thanks to
* Awesome people behind [elixir](elixir-lang.org), [phoenix](phoenixframework.org) and other libraries in the ecosystem
* Service providers [heroku](https://www.heroku.com/home) and [mongolabs](https://mongolab.com/) for their free tier service
## License
MIT License
## ToDo
* Ability to add custom templates via config
* 404 page to redirect to add new url
* Responsive mobile friendly UI?
## Sins
* Low test coverage
* Duplicated markup for adding response headers
Laziness and curiosity to see it working has been the reason for above sins. Plan to clean up if more people want to make changes to this code.