Testing Switching from MSTest to NUnit script We’ve been using MSTest for quite some time but now it’s time for change. First of the reasons for changing unit testing framework. We’re now building with Hudson/Jenkins which NUnit integrates better with. According to rumours NUnit is faster than MSTest. In the long run hopefully
Testing Running tests on filechange Ever since I saw a video of Corey Haines running Autospec I’ve been looking for an option to automatically run my tests when files change. So here is a list of different solutions. I found a python package that allows me to do what I wanted to do with
Books Book Review: Growing Object-Oriented software guided by tests Finally I finished reading Growing Object-Oriented software guided by tests, by Steve Freeman and Nat Pryce. We ran it as a reading circle at RemoteX but I think I’m the only one that will finish it, and I did so last week. So the circle quickly lost it’s
JavaScript The power of nested describes in Jasmine I’m experimenting with the Jasmine JavaScript testing framework to see if I can create a cucumber style testing framework using JavaScript. I want to go full out TDD on it so I started with a feature file, now I’m working on a spec to get that file running.
Testing What if I worked with a story to being with? I’ve been working on a pet project, just to see if my idea was possible at all. Central to the idea was sharing of content between users, and I wanted to see if I could build a model to make it work on Google AppEngine. Now I started out
Testing Running tests as files change I mentioned earlier a solution where Eclipse would run all my Python tests when I save a file. This is very convenient when using TDD in languages that can run tests fast. However that solution is tied to Eclipse and as I like Vim more and more I stand without
Testing Working with Jasmine I’ve been working extensively with JavaScript these past weeks. As I mentioned earlier I wanted to try out Jasmine and I definitively got the chance. I’ve been using it for all my testing needs these last weeks, and I love it. What do I like about Jasmine? The
Testing Unit-testing writing styles in QUnit (JavaScript) vs xUnit/MSTest Every now and then there are people doing experiments with different ways to name tests. The first time I was inspired to adopt a new way to name my tests was after Corey Haines performance kata (no I wasn’t there I saw the video, thanks Gregg). I really enjoyed
Design Bananas! During Android Only Erik Hellman from Sony Ericsson explained how they create their Android Phones. During his talk he mentioned that they put all phones through a monkey test. Where a phone has to sit for days with random input on the phone, without crashing. Naturally the thought is, I
Books Stress and TDD In Blink the author describes that there is an optimum peak of performance in regards to stress. What happens after that peak is reduced performance, inability to act on details and tunnel-vision so on. In programming this means we will see the end goal, often the finished functionality according to
Google Specifying tests The latest post on the Google Testing blog is quite interesting. Philip Zembrod discusses the readability of code developed by TDD and found that sometimes reading the test first didn’t always help to understand the written code. He makes a valid point. I started objecting to using mocks when
AppEngine Testing on Google AppEngine (Python SDK) Testing in Python and Django is pretty straight forward. However I wanted to write tests that assert email sending, URL fetching and other external sources. Making sure the intended code is executed and allowing me to write fuller tests. These external actions are accessed through Google’s API, and there
Testing Testing without mocking framework I had it pointed out to me at the end of last year that I use Mocks too much. I isolate the class under test more than I might need to do. Isolation of a class has the most value at service boundaries. If other classes can safely be included
GTD Test-list Funny thing. Some might remember my how I work with code, where you keep a list of issues you figure out as you work with the code. Apparently Kent Beck presents this as a pattern called Test List. I’m trying to embed it below, we’ll see how it
Testing My testing behavior has changed Quite interesting. We just finished an internal TDD course at RemoteX. During it I noticed one thing. How I write tests have changed quite a bit, just over the last few days. Lately I’ve been doing a lot of testing in JavaScript using QUnit, and coming back from that
RemoteX Testing level + 1 I learned a new way to test objects the other day. We had a consultant over to talk about a TDD course he will be holding for RemoteX internally. During the discussion the suggestion to test an object by mocking the object itself came up. What you do is, you
JavaScript Testing JQuery AJAX communication code I developed a JQuery Application using TDD these last couple of days. During the testing I used a new technique for testing my AJAX calls, so I thought I’d blog about how I test AJAX calls done by JQuery. First of you have to see that there are several
7Habits Seven habits and unit testing Some of the exercises covered in the previous post covered the aspect of analysing the end goal. Now, I’m sure that what we covered was no where near the available exercises. But doing several exercises servers a purpose, even if you already know your goal in life. Each exercise
People We need more automated tests During the end of the the 20th century, IBM had a TV commercial that I’m quite fond of. I can’t find it on YouTube, but its quite short. There are two suites talking, one reading a magazine. The one with the magazine says “We need to be on
GTD How I work with code the unit test part I wrote a blog post about how I work with code. The basic idea is that I record actions that I need to take as I work with the code in a format that is readable by the other developers in my team. In case I get run over by
Ajax IETester I found a new tool for testing web-applications in IE today. It’s called IETester, and it allows me to test IE versions 5.5 to 8 in the same application. Which is great, since my Vista machine only runs 8 normally. I use it to verify my Grails application