Test related information
Running a ping on all pages in the site
Follow these steps to run a quick fetch of all the pages of the system. The test runs against the production website for approximately 15 minutes.
git clone https://github.com/omalab/omatest.gitbundle installcucumber feature/project/whole_shebang.feature:3
Once the test is finished, make sure to visit the PaperTrail log and see if any of the web dynos have exceeded their memory. If so, restart them.
To change the target from the production website to the staging website, goto features/step_definitions/login_common.rb and changevisit 'http://omatestuser75inc.omaengine.com'tovisit 'http://omatestuser75inc.omamatic.com'
Miscellaneous
External site access during test run
The following external sites are accessed during test run
lsapi.seomoz.com/linkscape/url-metrics/
us.api.semrush.com/?type=phrase_this
us.api.semrush.com/?type=phrase_related
us.api.semrush.com/?type=domain_organic
us.fullsearch-api.semrush.com/?type=phrase_fullsearch
us.fullsearch-api.semrush.com/?type=phrase_this
us.fullsearch-api.semrush.com/?type=url_organic
api.ahrefs.com/get_backlinks_count_with_anchor.php
api.url2png.com/v3/
Google Trends/Insights
Tracker for pages that cause timeouts, memory exceeded errors and slow loading
May 29 2013 - Removed n+1 queries
Number of times memory exceeded during test suite - 4
H12 timeouts - 4
Total processing time for test suite - 613s
Slowest pages
May 28 2013 - Baseline
Number of times memory exceeded during test suite - 7
H12 timeouts - 7
Total processing time for test suite - (783s - first run; 550s - second run)
Slowest pages
Last updated