Skip to main content

Another Tech Develops Day!! Developing myself and developing others!

As of last Friday, another Tech Develops day is in the books!

It was an absolutely epic day, in true ASOS fashion (no pun intended) they just keep getting better and better! I had my special Tech Develops T-Shirt on and was ready to go!

I started off with hosting some 99 Second Talks, where we had ADMs, QAs and Developers talking for (you guessed it!) 99 seconds about topic(s) that they are passionate about! It didnt' even have to be Tech Related, we had one person talking about their love of Pugs, and what made this extraordinary was he joined the company just 3 days ago as a Princes Trust graduate! I don't think I would have had the confidence to have done something similar, so massive respect for that!

Image may contain: 6 people, people sitting

We had a talk about Conversational E-Commerce and what the future holds in that space, I spoke about Checking & Testing in a nice little poem that I'd created the night before (I felt massive pressure following the "success" of The Stickman Tester... I hoped this lived up to it). We had an ADM tell us how Rock & Roll and Software Development have some massive parallels! We also had talks about the Test Automation Pyramid (and what is wrong with it), what people learnt from James Bach coming to the office a few months ago and how sometimes Failure really isn't an option...There were many more!

Thanks to the awesome people at Ministry of Testing, they gave us all a free trial for the day for the DOJO, I found it difficult finding the time to make use of it, but I'm sure others used it! We'll be looking at how we can incorporate team licenses going forward hopefully.

Image may contain: 3 people, people sitting, table and indoor

In the afternoon I spent some time at a great talk about "Quality Quests", and it was great to see two people so passionate about the work they are doing, this particular talk is about gamifying some aspects of Continuous Improvements within teams and making it visible so that people can see what is happening, as all too often, teams become very much feature driven which can only lead to pain and heartache in the long run!

Image may contain: one or more people and people sitting

We finished up (before Friday drinks) with a round of TestSphere, as always, this was very enjoyable! We had people reminiscing or telling horror stories about how they have felt victimised in their role in the past, or we had people stalling whilst trying to think of a story! No matter what happened, it was a great way to get to know other QAs and to talk about things that have happened that other people may (or may not) relate to.

All in all, as with every Tech Develops day, I have finished it absolutely exhausted! It's not just about developing me, but it's about developing others and giving others the opportunity. I'm already making plans for the next one to top this one!


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…

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…