Skip to main content

What I learnt by NOT going to TestBash!

I've seen many blog posts about people posting about what they learnt by going to TestBash. It made me think about what I have learnt by NOT going to TestBash this year....

Firstly, I attended TestBash Brighton last year. I loved it, I learnt so much and came back passionate and engaged with the Testing Community. Over the course of the year however, my work changed significantly and I wasn't doing as much testing as I was before.

When TestBash came around this year, I had 3 QAs who asked about going. I said to them "Definitely go", we got the funding and got them tickets and off they went. I don't think they realised why I was so passionate about them going, and about how I was "gutted" that I wasn't going!

Image may contain: one or more people and closeup

So with 3 of the QAs who I work with being there, I was in constant communication with them, checking in on how it was going, what cool things have they learnt... They even brought me back an MoT Calendar and some TestSphere Cards! But that isn't all they have brought back...

They have brought back a fountain of ideas, they want to build up a community within ASOS (we have 150+ QAs - so we have the people), they want to try new games, go to new events, have ideas about what we can achieve within our domain... It's awesome to see them so invigorated and passionate!

I think that last one is important, Passion, I've learnt that it's very much something that needs to be nurtured, and it can stagnate, it can dwindle, but you need to get out and talk to other people to feed off of their passion, feed off of their enthusiasm and take that back into your workplace. Remember, smiling at someone can change someones day, in much the same way as showing and demonstrating passion towards something. It's infections.

I'm reading a book on how to build a successful community of practice, which I sent to one of the QAs who went, and she replied saying she'd bought the same book... Great minds think alike!

I have also learnt that I don't need to go, by sending people I work with, I get a lot out of it, and they get even more out of it. I'd much rather send others and let them experience it for the first time, than go again myself... Having said that I will be going again... It's just more important that others go!

One more thing I have learnt is that you can track so much stuff on Twitter! Every day during the conference/workshops I was checking the #TestBash on Twitter, it was almost like I was there... almost!

So, I feel that by sending 3 QAs, my passion for testing, for the community has been reinvigorated... hence the revival of this blog, and my first blog post in a LOOONNNNGGGG time. I have many more ideas lined up, but I thought I'd kick off with this as it's relevant and the reason why I feel invigorated about testing and the community again.

Comments

  1. Hi there! This is my first visit to your post! We are a collection of volunteers and starting a new initiative in a community in the same niche. Your post provided us useful information to work on. You have done a extraordinary job! SingHost

    ReplyDelete
  2. Your article is very useful, thanks for your information.We look forward for your valuable information.
    https://www.apponix.com/

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....

Tech Develops - A day dedicated to YOU!

Working in Tech, it can be difficult to find the time to further improve yourself, you're focused a lot on delivery, and it can be hard to drag yourself away from it and spend time on delivering an improved you. This is why some companies are starting to have time dedicated to your personal development, where people drop tools and do a personal project or watch some tutorials. Luckily working at ASOS we get the last Friday of every month to focus on this! Last Friday we held what we call a "Tech Develops" day, where as an employee of ASOS and working in Technology, In the week running up to it we decided it would be a good idea to have a platform where people could stand up and perform a 99 Second Talk about anything they please. We had 12 people sign up to it, and we had talks ranging from the technical (Git-Bisect) to a Conference review (UKStar). The first talk was an informative talk about Git Bisect and how it's used and why because of it, it's import...