If you don’t know by now, 5 months ago (5 months!!!) I joined Songkick.
One of the many things that appealed, apart from working with Amy of course, was to experience another way to develop software, namely Continuous Delivery.
So this post is a bit about, not getting stuck in your job, routine, thought processes, try something different when you can or if what you are doing doesn’t feel right!
How did I get into this topic?
Songkick has had quite a few new hires in the tech team over the past few months and as part of the on-boarding there is a an intro into how we test at Songkick.
For 2016 Amy has been mixing this up by making the session super interactive and it really works.
As part of this we spoke about exploratory testing over test plans and how your emotions can drive your journey through the system when you are hunting for information and bugs.
All this “huh!?”, “oh!”, “OH!?”, “ah”, and “erm” moments can drive your test journey through the application as a tester and developer.
On the flipp-side to this is boredom. Boredom is another emotional state to avoid. Question why you are bored. Have you exhausted your testing journeys, do you need to mix it up by using different devices?
Boredom and feeling a little stuck was what drove me to try something different.
First a quick back story.
As part of a merger in early 2015 Songkick is doing some re-aligning of technologies. To keep it as vague as possible. I have been part of one of those teams working towards one platform. This has been super exciting and provided a great learning experience as I could learn about both companies technological history.
But this means we have some (or a lot of) manual regression testing we do as a team. This is generally unusual for projects there but a way of providing confidence for the team and whole business.
Now where am I going with this?
My boredom (don’t tell my team, I keep telling them that all testing is fun) came from the fact that I was regression testing something that we did have confidence in, over and over again on different devices and browsers, but it is quite a risky project so we rather test twice and in person alongside automation.
In the retrospective I was surprised how concerned everyone was that the testing was left to one person while the rest of the team tries to finish off other tasks before the release date.
One of our team members had the great idea to block out some time and get everyone to test for an hour together.
Go with the energy.
Straight away I jumped at this and expanded on the idea. We discussed that this 1 hour session will involve all team members and we will test on different devices and browsers.
I was however not keen on providing a list of testing tasks or test plans as I wanted everyone to feel free to explore, so I created some user scenarios for everyone to have and try. They were meant as inspiration of what to test and a way of visulaisin how the software may actually be used.
This seemed to work well, although the volume of scenarios I supplied was frightening some initially, but by emphasising that these were ideas and did not have to be ticked off we got somewhere really quickly.
Make it as easy as possible.
One major thing with testing systems can be the test data. This can be time consuming to create and manage, putting people off spending time on testing. I took this away from the team and provided them with different test data options for the various scenarios. These were the same selection of test data meaning we had a mini performance test of several users, accessing the same data. Being in ticket sales though we generally deal with short and high spikes of data which we are testing using automation. 🙂
This can be as simple as buying jaffa cakes or bringing in some home made cookies. Always works a treat!
We had a focused testing session and logged several issues. None of which will block our release, thank god, but some which would have taken ages to find for one person.
Also we logged improvements on usability, as our designers and usability experts took part and got to experience the app first hand in a repetitive situation.
Overall this was a success, we got many eyes and devices to be used at the same time and it was a great team experience!
So don’t get stuck but do try something new! You never know what you may achieve.