Created
November 29, 2011 22:56
-
-
Save ordinaryzelig/1407000 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Pending: | |
| HomeController posts exposure exposes posts related to a specific network if params[:timeline_network_type] is given | |
| # Not Yet Implemented | |
| # ./spec/controllers/home_controller_spec.rb:22 | |
| ListenersHelper add some examples to (or delete) /Users/ningj/dev/projects/sv_studio/spec/helpers/listeners_helper_spec.rb | |
| # Not Yet Implemented | |
| # ./spec/helpers/listeners_helper_spec.rb:14 | |
| Resque::Failure::RetryNotifier stores failures in redis in addition to sending notifications. | |
| # Not Yet Implemented | |
| # ./spec/lib/resque/failure/retry_notifier_spec.rb:202 | |
| Resque::Failure::RetryNotifier deliver_brand_email does not deliver notifications if counter != (9 || 119) | |
| # Not Yet Implemented | |
| # ./spec/lib/resque/failure/retry_notifier_spec.rb:128 | |
| ResqueFailureNotifier instructions cc's a list of brand admins | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:12 | |
| ResqueFailureNotifier instructions bcc's the support team | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:13 | |
| ResqueFailureNotifier instructions contains a link to the sent inboxes | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:14 | |
| ResqueFailureNotifier instructions contains the publisher's first name | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:15 | |
| ResqueFailureNotifier instructions contains the sent time and date | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:16 | |
| ResqueFailureNotifier instructions contains the post message | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:17 | |
| ResqueFailureNotifier instructions contains the brand name | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:18 | |
| ResqueFailureNotifier instructions contains the network type | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:19 | |
| ResqueFailureNotifier instructions contains the network account name | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:20 | |
| ResqueFailureNotifier instructions sets @scheduled_at to #created_at if post was not scheduled | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_notifier_spec.rb:21 | |
| ResqueFailureSystemNotifier instructions contains the publisher's email | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_system_notifier_spec.rb:13 | |
| ResqueFailureSystemNotifier instructions contains the exception | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_system_notifier_spec.rb:14 | |
| ResqueFailureSystemNotifier instructions contains the queue | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_system_notifier_spec.rb:15 | |
| ResqueFailureSystemNotifier instructions contains the worker | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_system_notifier_spec.rb:16 | |
| ResqueFailureSystemNotifier instructions contains the payload | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_system_notifier_spec.rb:17 | |
| ResqueFailureSystemNotifier instructions renders the subject | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_failure_system_notifier_spec.rb:18 | |
| ResquePermanentFailureNotifier instructions cc's a list of brand admins | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:12 | |
| ResquePermanentFailureNotifier instructions bcc's the support team | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:13 | |
| ResquePermanentFailureNotifier instructions contains a link to the sent inboxes | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:14 | |
| ResquePermanentFailureNotifier instructions contains the publisher's first name | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:15 | |
| ResquePermanentFailureNotifier instructions contains the sent time and date | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:16 | |
| ResquePermanentFailureNotifier instructions contains the post message | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:17 | |
| ResquePermanentFailureNotifier instructions contains the brand name | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:18 | |
| ResquePermanentFailureNotifier instructions contains the network type | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:19 | |
| ResquePermanentFailureNotifier instructions contains the network account name | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:20 | |
| ResquePermanentFailureNotifier instructions sets @scheduled_at to #created_at if post was not scheduled | |
| # Not Yet Implemented | |
| # ./spec/mailers/resque_permanent_failure_notifier_spec.rb:21 | |
| RetryFailureNotifier instructions cc's a list of brand admins | |
| # Not Yet Implemented | |
| # ./spec/mailers/retry_failure_notifier_spec.rb:12 | |
| RetryFailureNotifier instructions bcc's the support team | |
| # Not Yet Implemented | |
| # ./spec/mailers/retry_failure_notifier_spec.rb:13 | |
| RetryFailureNotifier instructions sets @scheduled_at to #created_at if post was not scheduled | |
| # Not Yet Implemented | |
| # ./spec/mailers/retry_failure_notifier_spec.rb:14 | |
| FacebookEndpoint persist_posts stores network users activities on given post | |
| # Not Yet Implemented | |
| # ./spec/models/facebook_endpoint_spec.rb:40 | |
| NetworkEndpoint fetch_posts returns true instead of posts from database if endpoint has been updated in last 10 minutes if refresh_only => true is passed | |
| # Not Yet Implemented | |
| # ./spec/models/network_endpoint_spec.rb:22 | |
| NetworkPost user_sentiment= sets the calculated_sentiment to whatever the user_sentiment is when set | |
| # Not Yet Implemented | |
| # ./spec/models/network_post_spec.rb:9 | |
| Network | |
| # Not Yet Implemented | |
| # ./spec/models/network_spec.rb:67 | |
| Post blocked_words lists blocked words in post | |
| # Not Yet Implemented | |
| # ./spec/models/post_spec.rb:493 | |
| Post deliver_retry_failure_notifications delivers mail to brand admins when status is changed from failed to delivered | |
| # Not Yet Implemented | |
| # ./spec/models/post_spec.rb:997 | |
| TwitterNetwork refresh_relationships rescues from failures so processing can continue | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_network_spec.rb:58 | |
| TwitterNetwork publish returns a hash with an id and response_data key | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_network_spec.rb:171 | |
| TwitterNetwork TwitterNetwork publish with a public message immediately creates corresponding TwitterPost at appropriate endpoints on network | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_network_spec.rb:160 | |
| TwitterNetwork posts includes retweets | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_network_spec.rb:463 | |
| TwitterPost update_or_initialize_from_response retweets sets activity object_identifier to id of status retweeted | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:199 | |
| TwitterPost update_or_initialize_from_response retweets sets activity target_author_id to id of user who retweeted | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:200 | |
| TwitterPost update_or_initialize_from_response retweets sets activity target_author_name to name of user who retweeted | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:201 | |
| TwitterPost update_or_initialize_from_response direct_messages sets activity target_id to id of message message is reply to | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:211 | |
| TwitterPost update_or_initialize_from_response direct_messages sets activity target_author_id to id of user who sent originating message | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:212 | |
| TwitterPost update_or_initialize_from_response direct_messages sets activity target_author_name to name of user who sent originating message | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:213 | |
| TwitterPost update_or_initialize_from_response mentions adds a correlated network_post_activity with a verb of mention | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:217 | |
| TwitterPost update_or_initialize_from_response mentions sets activity target_id to id of status status is reply to if applicable | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:222 | |
| TwitterPost update_or_initialize_from_response mentions sets activity target_author_id(s) to id of user mentioned | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:223 | |
| TwitterPost update_or_initialize_from_response mentions sets activity target_author_name(s) to name of user mentioned | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:224 | |
| TwitterPost initialize_from_response updates existing post attributes | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:246 | |
| TwitterPost initialize_from_response stores network users activities on given post | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:248 | |
| TwitterPost retweets fetches posts corresponding to network post activities of verb retweet performed on posts owned by networks passed | |
| # Not Yet Implemented | |
| # ./spec/models/twitter_post_spec.rb:394 | |
| User validates_format_of alternate_email should accept a nil value | |
| # Not Yet Implemented | |
| # ./spec/models/user_spec.rb:10 | |
| Organization account activity reports can be ordered by clicking on a certain column header | |
| # Test passed so far, but could stand to be more thorough | |
| # ./spec/requests/organizations/reports/account_activity_reports_spec.rb:27 | |
| Organization account activity reports it should behave like reports that filter by brand filters to selected brand | |
| # Can't test any further without a JavaScript enabled driver: submit on change form | |
| # ./spec/support/shared_examples/reports_that_filter_by_brand.rb:14 | |
| Posts by status reports displays posts of status type specified by user | |
| # Can't test any further without a JavaScript enabled driver: submit on change form | |
| # ./spec/requests/organizations/reports/posts_by_status_reports_spec.rb:23 | |
| Posts by status reports can be ordered by clicking on a certain column header | |
| # Test passed so far, but could stand to be more thorough | |
| # ./spec/requests/organizations/reports/posts_by_status_reports_spec.rb:39 | |
| Posts by status reports it should behave like reports that filter by brand filters to selected brand | |
| # Can't test any further without a JavaScript enabled driver: submit on change form | |
| # ./spec/support/shared_examples/reports_that_filter_by_brand.rb:14 | |
| Organization scheduled posts reports can be ordered by clicking on a certain column header | |
| # Test passed so far, but could stand to be more thorough | |
| # ./spec/requests/organizations/reports/scheduled_posts_reports_spec.rb:22 | |
| Organization scheduled posts reports it should behave like reports that filter by brand filters to selected brand | |
| # Can't test any further without a JavaScript enabled driver: submit on change form | |
| # ./spec/support/shared_examples/reports_that_filter_by_brand.rb:14 | |
| Organization system activity reports can be ordered by clicking on a certain column header | |
| # Test passed so far, but could stand to be more thorough | |
| # ./spec/requests/organizations/reports/system_activity_reports_spec.rb:25 | |
| Organization system activity reports it should behave like reports that filter by brand filters to selected brand | |
| # Can't test any further without a JavaScript enabled driver: submit on change form | |
| # ./spec/support/shared_examples/reports_that_filter_by_brand.rb:14 | |
| Finished in 244.47 seconds | |
| 1347 examples, 0 failures, 66 pending |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment