Skip to main content

NxtGenTesting Conference

I've just bought my ticket for the NxtGenTesting Conference on May 23rd. A number of talks are appealing to me, but these are just some of the highlights for me personally and why:


  • Building agile automated test scripts with Selenium WebDriver - This is a big highlight for me, and reason enough to go alone in my eyes. I've got a fair amount of experience with Selenium WebDriver, but only in one company, so I'm really looking forward to seeing how other people do it and to discuss the pros and cons of each approach.
  • Mobile Testing - Obviously with such an increased amount of traffic coming through mobile devices to any website and with mobile browsing predicted by some to overtake fixed internet browsing in 2014, I'm interested to see how we can ensure they have the best experience as possible, but obviously this means testing on a number of new devices and OS, how can we manage that? I have a few ideas, mainly about prioritising user traffic and browser engines based on visits, but i'm interested to see how other people are going to achieve this, and more importantly make it manageable.
  • What new skills should testers be acquiring and gathering - I'm always interested to learn new things, and discover what new technologies are out there, so will be paying special attention to this one, I'm also interested in what other testers deem to be important for their field, and I can hopefully share what I know and what I think are good skills for a tester to have.
There's also a number of speakers who I'm interested in hearing speak, having followed their blogs and agreeing with a lot of what they say, for instance I've linked to Paul Gerrards blog in the past (namely this post here), and he's speaking, so I'll be sure to listen to what he has to say.

All in all I'm pretty excited!

Comments

Popular posts from this blog

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.

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

        private s…

Famous Movie Quotes applied to Software Engineering - Jaws

You're gonna need a bigger boat? How can that relate to Engineering?

Firstly, let me ashamedly admit, that I've never seen the whole of Jaws all the way through. It's on my list of films to watch, but whether I get round to it, is another matter!



Anyway, to apply this to engineering, it's almost like "you're gonna need more testers/developers"...

We hear this all too often when trying to push releases out the door, let's throw men at it... However, as we all know, a bigger boat/more men... isn't always the answer, it's not a guarantee of quality, or even a guarantee of getting things done quicker.

If you have a task that will take 2 hours, simply having 2 people work on it doesn't mean that it is halved, in fact often, the time taken to do the task remains at 2 hours, but the maintainability and the knowledge around that area is increased, so it's a price, in my opinion that is often worth paying.