app

Internals Visible To

2012-01-18

I was working on an HttpModule today that I will try and blog about later. I wanted to make an interface that I was programming against internal. This of course broke my unit tests. Luckily I remembered that you can make internals visible to other assemblies such as test assemblies. I just couldn’t remember how.

This stackoverflow post had the answer. The line of code below needs to be added to the assembly.cs file located in the project with the internal code.

[assembly: InternalsVisibleTo("name of assembly here")]

Since I am using Moq for mocking, I also had to make the internals visible to the castle dynamic proxy. I found out how to do that on this post. You just have to add the line below:

   [assembly: InternalsVisibleTo("DynamicProxyGenAssembly2")]

Capybara InvalidSelectorError - Selenium Issue 2099

2011-08-24

This morning I tried running our entire capybara suite and a ton of tests failed due to an issue with the Selenium Webdriver. It took some searching and tinkering to come up with the fix below.

The following links were very helpful and provided most of the patch below that I added prior to the code that runs the tests:

BDD for JavaScript with Jasmine

2011-08-17

Both peepcode and tekpub have done excellent screencasts on using backbone.js in the last couple of months. In peepcode’s screencasts, they used a JavaScript BDD framework that was very intriguing called Jasmine.

From the Jasmine home page:

Jasmine is a behavior-driven development framework for testing your JavaScript code. It does not depend on any other JavaScript frameworks. It does not require a DOM. And it has a clean, obvious syntax so that you can easily write tests.

Here is a non trivial example of some specs I wrote for a recent enhancement request.

The example above uses a handy plugin for the fixtures called jasmine-jquery. One gotcha to look out for when using the fixtures is that current versions of chrome do not allow file:// URI without an override. You can start Chrome with the —allow-file-access-from-files condition to get around this.

One other plugin that comes in handy when using Jasmine (though not used in the example above) is Sinon. Sinon provides standalone test spies, stubs and mocks for JavaScript. It has no dependencies, and works with any unit testing framework.

Knockout JS

2011-08-06

I have known about knockout.js for quite a while now. It’s one of those libraries that gets a lot of coverage, I just haven’t had the time to check it out.

From the introduction:

Knockout is a JavaScript library that helps you to create rich, responsive display and editor user interfaces with a clean underlying data model. Any time you have sections of UI that update dynamically (e.g., changing depending on the user’s actions or when an external data source changes) KO can help you implement it more simply and maintainably.

Check out my Hello World fiddle below:

On the result tab, notice if you edit one of the inputs, the text below changes automatically.

As I built out the eventual page I decided to try knockout out on, the following resources were very helpful:

The knockout documentation – it’s very good
Articles on Ryan Niemeyer’s blog

Check Active Element with Capybara

2011-08-06

The other day, I wanted to test that a certain element had the focus with capybara. This is what I came up with:

assert(@s.evaluate_script('document.activeElement')[:id] == 'IdOfElement', 'The element did not have the focus')

Note: @s is my session. I am managing session myself as I am testing a non rack app.

My Vim Setup on Windows

2011-07-27

I have been slowing teaching myself how to use vi/vim for quite some time now. I have been using a Visual Studio plugin called ViEmu and I have also been using MacVim some on my Mac. A few days ago I decided to also install gVim and use it on windows in situations where I don’t need the overhead of Visual Studio.

I am using this post to document how I setup gVim for use on my windows machine. Below are the settings I have added to the _vimrc file:

Here is the documentation on where they came from:

Fonts

http://vim.wikia.com/wiki/Setting_the_font_in_the_GUI

Tabs and Spaces

http://vim.wikia.com/wiki/Converting_tabs_to_spaces

Line Endings

Color Scheme

No backup

http://stackoverflow.com/questions/2197749/gvim-on-windows-way-to-disable-the-tmp-file-cretion

Line Numbers

http://vim.wikia.com/wiki/Display_line_numbers

Quick way to use Amazon CDN with toto

2011-07-22

Just a few days back Amazon released an official Ruby SDK for Amazon Web Services (AWS). I found out about it through an introductory article on rubyinside.com.

I figured writing a quick script to upload my toto public folder to S3 would be a neat way to explore the new SDK. The script below is very simple. It just iterates through my public folder and uploads each item to my S3 bucket.

I ran into a couple of issues along the way though that you should be aware of:

I wasn’t happy with the auto detection of mime types that Amazon was doing. For example, an uploaded png was getting a mime type of image/jpeg when downloaded. I fixed this by explicitly setting the content type for each uploaded item. I did this using the built in mime library.
I initially uploaded my fonts to S3, but currently AWS does not have the ability to send the Access-Control-Allow-Origin header that Firefox requires before it will serve a font from another domain (rubystatic.beckelmans.com in this case). I ended up having to continue to serve my fonts from the beckelmans.com domain.

Close the Browser After Each Capybara Test

2011-07-11

I have been using Capybara to test a non rack based app. Basically I am just pointing it at URL and am then managing my own sessions. Until recently, I was not properly closing the browser after each test and if I ran I full suite of tests would end up with many, many open browser windows that would get closed only once the full suite had been run.

This was easy to remedy. There is an instance method on Capybara::Selenium::Driver called quit that does exactly what you would guess.

def setup
  @s = new_session
end

def teardown
  @s.driver.browser.quit
end

Looking for non ASCII Characters with Capybara

2011-07-09

I was trying to test some internationalized pages with capybara this week and kept running into problems. In my test, I was trying to make sure that the prices on our UK pages showed British pounds £ instead of US dollars $.

Before I could even run the test, I was running into an invalid multi-byte character error:

I remembered reading that one of the big changes with Ruby 1.9 was encoding. It took some Googling and experimentation, but the test is now working. I did the following:

I saved my files as UTF-8 (I am working in Visual Studio which does not use UTF-8 by default and is generally set on a US machine to Western European Code Page 1252). You can change the encoding by selecting Save As from the File menu and then choose to save with encoding.
I then added a comment at the top of my Ruby test file to hint to the parser that the page is UTF-8 as shown below:

# encoding: utf-8

Using a Custom Firefox Profile with Capybara

2011-07-07

I wanted to be able to test some internationalization using capybara with a non rack app. You cannot set request headers using the selenium driver, so I had to find a different way. What I came up with was using a custom Firefox profile since the profile to use can be set when you setup the capybara driver to use.

Capybara.register_driver :selenium_firefox_gb do |app|
    Capybara::Selenium::Driver.new(app, :browser => :firefox, :profile => "gb")
end

In the Firefox profile, I set the default language as I desired, but you could also tweak other things like the user agent string.

Tools > Options > Content > Languages