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!
Labels:

Comments

Post a Comment

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 follow...
68 comments
Read more

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...
14 comments
Read more

The Stickman Tester... The full version complete with deleted "scenes"!

As some of you may have seen, a little while ago I performed a 99 second talk on the Stickman Tester for the Ministry of Testing. Owing to the fact that it had to be 99 seconds, this unfortunately meant that a verse was left out in order to keep it within the time frame! It's only now that I have found the time to put the deleted verse/scene back in, and re-record it and upload it! (It's now a 120 second talk!) It talks about a testers journey in an Agile team, about how not everybody has it as good as others, and basically talks about not giving up, keep searching, or trying to change your role to make it what you want it to be. Anyway, here it is, in all it's glory. Hope you enjoy it!
15 comments
Read more