| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |
| function declOfNum(number, titles) { | |
| cases = [2, 0, 1, 1, 1, 2]; | |
| return titles[ (number%100>4 && number%100<20)? 2 : cases[(number%10<5)?number%10:5] ]; | |
| } | |
| use: | |
| declOfNum(count, ['найдена', 'найдено', 'найдены']); |
| <!DOCTYPE HTML> | |
| <html lang="en-US"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title>test upload by chunk</title> | |
| </head> | |
| <body> | |
| <input type="file" id="f" /> | |
| <script src="script.js"></script> |
| (function (window) { | |
| // This library re-implements setTimeout, setInterval, clearTimeout, clearInterval for iOS6. | |
| // iOS6 suffers from a bug that kills timers that are created while a page is scrolling. | |
| // This library fixes that problem by recreating timers after scrolling finishes (with interval correction). | |
| // This code is released in the public domain. Do with it what you want, without limitations. I do not promise | |
| // that it works, or that I will provide support (don't sue me). | |
| // Author: rkorving@wizcorp.jp | |
| var timeouts = {}; |
| /** | |
| Workaround for iOS 6 setTimeout bug using requestAnimationFrame to simulate timers during Touch/Gesture-based events | |
| Author: Jack Pattishall (jpattishall@gmail.com) | |
| This code is free to use anywhere (MIT, etc.) | |
| Note: UIWebView does not support requestAnimationFrames. If your timer is failing during a scroll event, | |
| take a look at https://gist.github.com/ronkorving/3755461 for a potential workaround. | |
| Usage: Pass TRUE as the final argument for setTimeout or setInterval. |
On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.
Up until recently, a typical unit test for us looked something like this:
describe('views.Card', function() {
| /** | |
| * Wrap gulp streams into fail-safe function for better error reporting | |
| * Usage: | |
| * gulp.task('less', wrapPipe(function(success, error) { | |
| * return gulp.src('less/*.less') | |
| * .pipe(less().on('error', error)) | |
| * .pipe(gulp.dest('app/css')); | |
| * })); | |
| */ |
