Skip to main content

ASOS Testing Community - Coding Challenges #1

Here @ASOS we're trying to build a community for testing, and dare I say it, but it is slowly happening, over the past couple of months we've been getting real traction with regards to a community feel, attendance at our meetups but not just attendance but people voicing opinions and being passionate and wanting to improve themselves. 

Anyway, at the last meeting it was suggested that we do some coding challenges, some quick challenges that anyone can pick up and do, I understand that not everyone understands or knows how to write code, but by adopting a pairing approach it was hoped that everyone would get something from it.

Anyway, a colleague sent me this website: it has a long list of coding challenges that people have completed and whatnot, so I took about the task of finding a suitable coding challenge for the meeting. It was important to choose something that wasn't going to:

a) take too long to complete
b) be too hard to complete

Luckily, this didn't take too long and I found a suitable problem:
Each new term in the Fibonacci sequence is generated by adding the previous two terms. By starting with 1 and 2, the first 10 terms will be:
1, 2, 3, 5, 8, 13, 21, 34, 55, 89, ...
By considering the terms in the Fibonacci sequence whose values do not exceed four million, find the sum of the even-valued terms.
I thought this was challenging enough, but wouldn't take too long to complete, and if people finished it early, then it would be good/useful to write some unit tests for it...

I sent an email round before the meeting so that people could read up about it and have a think about a solution beforehand, and then hopefully come the meeting there'd be lots of discussions in the pair about how to approach the solution.

We had 4 groups of 2 turn up, and as luck would have it, the pairings worked our reasonably well with stronger coders in each of the groups. We'd even had people who had worked on the solution itself before the meeting, and whilst that wasn't really the point of the meeting, it showed 2 things:

  1. They were eager and willing to learn
  2. They came prepared and with ideas to share with their partner
So it's really difficult to complain about something like that! 

We had varying levels of success, although all but one completed the task at hand (and even they finished it after the meeting), we had many different approaches tried by the pairs, some of them used a list and then used LINQ to extract what was needed, some people just wrote one method that would do what was needed and some people even adopted a TDD approach and went about writing tests first that would then fail.

It also ties in with some other things I want to try and implement, and they're inspired from a recent conference I attended (Unicom - Next Generation Testing Conference) and a talk by Raji Bhamidipati where she discussed the benefits of Paired Testing, we've done things around Pairing before, and how it's not just for developers, so I'll definitely be trialing this out in future as well.

It's definitely something we will do again, perhaps even create a seperate session for completing coding challenges I guess it's about finding the right mix of technical challenges and discussions etc. It's definitely going to be an exciting few months in the Testing Community here! :)


  1. a friend of mine once asked me to give him instructions on coding now i can post your kind work check here for everyone to benefit from it.


Post a Comment

Popular posts from this blog

Advantages of using Test Management tools

Before I start talking about test management tools, let me clarify what I mean by the term test Management tools...  I am not taking about your office excel program where you store your test cases in. I'm talking about bespoke test Management tools, your quality centers or Microsoft test manager...
In the strict case of the term test Management tool, Microsoft Excel can be used as such, but heck, so could a notepad if used in the right way... For the sake of this blog post I am talking about bespoke test Management tools.
Firstly, what test tools are out there? There are many more out there today than when I first started in QA over 5 years ago. When I started the market was primarily dominated by a tool called Quality Center, this would run in a browser (only Ie unfortunately) and was hosted on a server.. Nowadays it's market share has somewhat dwindled, and there are some new kids on the block. 
One of the more popular tools is that of Microsoft Test Manager, it's big…

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used.

A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog.

The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now.

A Product Backlog Item is made up of the following:

Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that.

Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follows: 

By writin…

Dealing with Selenium WebDriver Driver.Quit crashes (Where chromedriver.exe is left open)

We recently came across a problem with Selenium not quitting the webdriver and this would then lock a file that was needed on the build server to run the builds.

We were using Driver.Quit() but this sometimes failed and would leave chromedriver.exe running. I looked around and found this was a common issue that many people were having. We (I say we, as we came to the solution through paired programming), came up with the following, that would encapsulate the driver.quit inside a task and if this task takes longer than 10 seconds, then it will clean up any processes started by the current process, in the case of the issue on the build server, it would kill any process started by Nunit.

        public static void AfterTestRun()
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))

        private s…