Brent Sordyl’s blog

So there I thought, why not just initiate a Sinatra application as part of your tests, and easily manage that sinatra as the mocked web service? WIN.

I created the SinatraFakeWebService gem that provides a simple interface to instantiate that Sinatra application and to manage the mocked webservice interface.
(Link: Using Sinatra to test remote services in Rails)

Uncategorized restful, ruby, sinatra, testing, web-services

“Product Development is an Art that involves many people & suffers from The Malkovich Bias”
(Link: Meetup.com’s Lean Usability Testing)

Uncategorized testing, usability

A developer tool for interacting with web services and other web resources that lets you make HTTP requests, set the entity body, and content type. This allows you to interact with web services and inspect the results.

After you install it, just go to Tools->Poster to open the poster window. After that, try a GET or POST on your favorite web service or site.
(Link: Poster :: Add-ons for Firefox)

Uncategorized development, restful, testing

in this article we are going to focus more specifically on cross-browser compatibility. Building websites to work properly and look good in multiple browsers is a fact of life that web designers must deal with. It is probably one of the most frustrating aspects of designing for the web, but thankfully there are tools out there that can help and hopefully keep you from pulling all of your hair out.
(Link: Useful Tools for Testing Cross Browser Compatibility | Web Design Ledger)

Uncategorized cross-browser, testing

As companies look to their peers and audiences to help define product features, there’s a greater need for scalable testing platforms. Here’s a summary of eight useful services that will help put you on the path to product greatness.
(Link: Always Be Testing: 8 Services For Usability Feedback)

Uncategorized crowdsourcing, testing, usability

To help you understand how everyone sees your website, we created a tool called Browser Size in our 20% time. Browser Size is based on a sample of data from visitors to google.com. Special code collects data on the height and width of the browser for a sample of users. For a given point in the browser, the tool will tell you what percentage of users can see it. For example, if an important button is in the 80% region it means that 20% of users have to scroll in order to see it. If you’re a web designer, you can use Browser Size to redesign your page to minimize scrolling and make sure that the important parts of the page are always prominent to your audience. We hope people will use this tool to make their websites better, in turn making the web better for everyone.
(Link: Official Google Blog: Browser Size: a tool to see how others view your website)

Uncategorized cross-browser, testing

Go Test It helps you create better web apps in less time. With our automated test infrastructure you can continuously verify that your web application or website works correctly in many different browsers.
(Link: Go Test It – Automated Cross-Browser Functional Testing (GoTestIt))

Uncategorized cross-browser, testing

Let’s take one thing off the table, there is NO tool problem. Most automation tools do the same thing, catalog objects, record and playback and advanced scripting abilities, so, please, if you trying to organize an automation project, don’t make it about a tool (I think I’m famous for saying this, since tools are only means to an end, they aren’t panaceas, in fact that’s the last thing they are).
(Link: Automation Adoption)

Uncategorized automatedtesting, testing

(Link: Final Builds Site – Internet Explorer Collection)

Uncategorized cross-browser, testing

In this article, you’ll learn how the mocking capabilities of GrailsUnitTestCase and ControllerUnitTestCase make it easy to unit test Grails artifacts that you’d otherwise assume need to be tested using an integration test. The mockForConstraintsTests(), mockDomain(), and mockLogging() methods all leverage Groovy’s metaprogramming magic to make testing your domain classes, services, and controllers a breeze.
(Link: Mastering Grails: Mock testing with Grails)

Uncategorized grails, groovy, testing

Instead of writing a bunch of test code to go through all the various permutations that could result in errors on the front-end, I found GoogleBot (Google’s web crawler) was doing a pretty good job of scanning the whole site in a timely manner. I set up code on the front-end to email me anytime there is a Server Error. I found early on that when I’d push out new changes, GoogleBot would find obscure bugs with infrequently visited pages much quicker than I (or even my users) could.
(Link: Meet StatSheet’s Lead QA Tester: GoogleBot – StatSheet.com ChangeLog)

Uncategorized testing

rcov is a code coverage tool for Ruby. It is commonly used for viewing overall test coverage of target code. It features:

* fast execution: 20-300 times faster than previous tools
* multiple analysis modes: standard, bogo-profile, “intentional testing”, dependency analysis…
* detection of uncovered code introduced since the last run (”differential code coverage”)
* fairly accurate coverage information through code linkage inference using simple heuristics
* cross-referenced XHTML and several kinds of text reports
* support for easy automation with Rake and Rant
* colorblind-friendliness
(Link: rcov: code coverage for Ruby)

Uncategorized coverage, ruby, rubyonrails, testing

Metric_fu is a set of rake tasks that make it easy to generate metrics reports. It uses Saikuro, Flog, Flay, Rcov, Reek, Roodi, Subversion, Git, and Rails built-in stats task to create a series of reports. It’s designed to integrate easily with CruiseControl.rb by placing files in the Custom Build Artifacts folder.

New in metric_fu 1.1.0 is integration of the ‘Awesome’ template and graphs — which graph your metric performance over time! Big thanks go to Nick Quaranto and Edouard Brière for their work on this feature. If you’re used to the non-awesome reports then this will be quite a treat. Graphing requires the gems ‘gruff’ and ‘rmagick’ (and rmagick requires ImageMagick). If that’s too much installation to bear, then see configuration section below for how to turn off graphing of the metrics.
(Link: metric_fu: A Ruby Gem for Easy Metric Report Generation)

Uncategorized metrics, ruby, rubyonrails, statistics, testing

Heckle is a great new library from Kevin Clark (though Ryan Davis wrote a proof of concept at RubyConf) that ‘torments your tests’. It uses ParseRuby and RubyToRuby to rip your code apart and forces random data into your code (currently it does this for strings, symbols, regexps, ranges, booleans, and numbers) to see how good your tests really are.

Simply, it’s fuzz testing for your Ruby tests, and that’s a good thing if you want your test suites to be strong and far-reaching.
(Link: Heckle: Tortures Your Tests For Revealing Confessions)

Uncategorized coverage, ruby, rubyonrails, testing

Browser Sandbox – Run any browser from the web
Microsoft Internet Explorer 8, Internet Explorer 7, and Internet Explorer 6
(Link: Browser Sandbox – Run any browser from the web)

Uncategorized browser, cross-browser, testing