| # Model | |
| expect(@user).to have(1).error_on(:username) # checks whether there is an error in username | |
| expect(@user.errors[:username]).to include("can't be blank") # check for the error message | |
| # Rendering | |
| expect(response).to render_template(:index) | |
| # Redirecting |
I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)
Note: this was written in April/May 2014 and the API may have changed since. I have nothing to do with Tinder, nor their API, and I do not offer any support for anything you may build on top of this
I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)
Note: this was written in April/May 2014 and the API may have changed since
Put this code on the page where the form you want to track resides. Some other examples are currently passed around the web with varying quality. This is one that will work as long as your form tag has an id= or name attribute.
You don´t have to change this code to be able to track form abandonment in your shopping cart, order form or whatever form you want.
This sends events to Google Analytics when a user focuses somewhere not in a field after having focused on a input field. You won´t know for how long users focused on respective fields, or the actual conversion rate in the form using this, but it might be a start.
A tool that provides more insight both over time and per field, is Form Analytics wich helps you optimize your online forms. For instance, it measures dropout rate, average field input length, conversion rate and average time per field. All which provides great insights in the most overlooked, yet important part of you site.
Anyway, here´s the code:
| # | |
| # zsh function to start Foreman based on whether or not | |
| # you have multiple Procfiles | |
| # | |
| # we are adopting this schema of having environment | |
| # specific Procfiles: | |
| # | |
| # config/development.proc | |
| # config/stage.proc | |
| # config/production.proc |
| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |
