Update: Sam Connelly Tester Profile V2
I used canva to create a resume, I had fun putting it together. You can view V1 here: Sam Connelly Tester Profile
I enjoy new experiences, this is almost to my detriment. As an example, I find it hard to walk past a new fancy cafe without walking in. I try not to be materialistic and attached to my possessions. I do not achieve this all of the time but it means I prefer to buy second hand, I’m not sentimental towards my possessions and I try to buy only what I need.
Now values don’t have to be perfect, they are inspirational. This is what I aspire to be. Sometimes I don’t get them right all of the time but when faced with a difficult decision, hopefully I can use my values to help guide me.
Co authored with Brian Osman
Often at Tyro, we’ve thrown a tester into a team with developers with little structure. The testers and their teams are encouraged to make their own process. I’m tempted to call this free range testing (hence the title of the blog), it’s like letting the tester roam free to see what happens.
We acknowledge that there are no best practices, testers use the context of their team and their risk radars to drive their testing efforts. Testers have different interests, skills and risk radars and this feeds into their unique way of testing. We also acknowledge that testing is a team effort, the tester is a positive influence in their teams testing approach/culture.
This was also stressful, my first 3 months felt like I was drowning and many testers sympathise with this feeling. There is the information overload of working in a new company, often a new industry for most new testers and there is also the stress of trying to figure out how to add value to the team/company. The lack of structure compounds the “sink or swim” feeling. Around this time, I was struggling with a nerve injury and a relapse of depression.
We’ve tried different approaches to ease that stress, some testers may spend a week or two getting familiar with the context of Tyro before being dropped into a team, we now mimic part of the Developers on boarding process too. I’ve recently been pairing for a few half day sessions with a new tester to help them get on board; to help navigate the language, tech and business context. I also get to expose this new tester to my attempts at influencing the testing approach within my team. fresh meat, mwuhahaha.
We have moved from having the test team being outside the engineering practice, isolated and a gatekeeper to being embedded within the engineering practice; where the tester is the champion of testing for their team. We couldn’t have done this change without Anne-Marie.
Champions of Testing
By definition, a champion is someone(s) who;
enthusiastically supports, defends or fights for a person, belief, right or principle.
Each tester is a champion of testing by becoming a champion for testing. By the value of work that is undertaken and the value added to their delivery team, a tester can very quickly increase their credibility. As an oft-times lone tester amongst developers, the credibility card should not be underestimated nor discounted. Increasing credibility and value can help a tester champion (that is to say enthusiastically support, defend or fight) the idea that testing is important and vital to modern software development.
When we talk about testing, we are meaning software testing which in one form is;
executing a program with the intent of finding errors” (Myers, 1976)
“… a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimise the value of her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project.” (Kaner, 2006).
At Tyro, the encouragement is for testers use their personal freedom to continually optimise the value of her work or in other words, become context driven. The context allows the tester to optimise their approach to testing in both an individual sense (for example exploratory testing, using scripts, tools, test cases, scenarios or whatever may be useful) and in a team sense (for example test strategies, processes, developer tests, team quality and so forth). By so doing, the Tyro tester champions testing by the valued added work that they do.
In a larger sense, a Tyro tester is also encouraged to contribute amongst the tribe(s) and Engineering as a whole. This may be achieved by the work done in different guilds or being involved in different initiatives. A tester may also deliver compelling tech talks which in turn help increase their standing within the engineering community. This helps fuel a testers sphere of influence and thereby championing testing.
Sometimes though a tester may need to be more forthright in their approach with the team by advocating for quality or taking lead in different initiatives. A example of this was the Java de-serialisation issue whereby Marina (as a member of the security cabal) and working alongside developers, took the lead in making sure that the various team areas this issue touched was tested by the appropriate tester. In this sense, the test team championed testing together with the work by the developers and helped provide a Tyro solution.
So why would this be considered championing testing? Unlike some places, Tyro gives people the opportunity to really use the skills that they have acquired and to be able to use them in a way helps the engineering aspects of Tyro to grow. Most often, Tyro will turn a typical corporate blame game sessions into meaningful and value learning sessions and this, alongside, the test work performed by testers, makes for a wonderful opportunity to showcase (or in other words champion) the value a tester can bring to a Tyro world that is predominately developer focused. Thanks to this and the guidance given at a test practice level, champions of testing is encouraged and ultimately allows a Tyro tester to produce their, valued approached to their team (aka free range testing).
In this regard, it has to be acknowledged that champions also included senior management who encouraged and led the idea that testing is absolute to helping good development to flourish. With the drive and encouragement from the top, Tyro has a culture of advocating quality and of the tester producing the best work that they can.
Formality and Ceremony vs. Freedom and Responsibility
In most companies that I’ve worked in (well, the larger ones anyway), there has often been a marked dependency on formality and ceremony. In one large 200+ tester shop, the formality that was determined by the development model, the high degree of separation from developers and over reliance on a large, expensive test management tool (as well as leadership from a mostly non-test, very conservative senior management group) meant that formality was the valued ‘value’ for that testing practice. Along with the formality, the ceremony required to either elicit requirements (as in elicit the requirements NOT stated in the functional specifications or test the words that were written) or present the screeds of artifacts that had to be producedto satisfy the development model, often meant that testers were relegated to writing and template filling as opposed to actual testing. I saw first hand the efforts put into creating documents outweighing the efforts put into actual test activity. As one of two senior managers who had relevant testing experience, the ability to make significant changes was hampered by the culture of the environment.
When i compare this with the culture at Tyro, it is like comparing night and day. The testing culture within Tyro lends itself the other way – towards freedom and responsibility. Now that is not to say that its chaos – from it. A culture of freedom and responsibility still requires guidance, process, frameworks if you will. The greater the freedom someone has, the greater the discipline that is required. This is essential in the current testing climate at Tyro whereby the testers have the freedom to determine the best approach to testing that will add value to their teams. Thankfully, we are not bound by some archaic, test management tool driven process but rather by what approach will best suit. In this regard, it was absolutely vital that the overarching culture allowed this happen otherwise great testers may not have had the opportunity to flourish.
Tyro has a culture of trust. I imagine this is one of those things that is easy to say but hard to live. There is no one asking me to justify my work. It’s up to me to create my own testing process with my team. Each tester has to come up with their own testing process. This can be stressful because it feels like no one is providing any guidelines or approach. The lack of formal structure is nerve wracking because that structure in a previous context use to be a comfort. That structure helped me to understand where I stood. I had to figure that out on my own at Tyro. We trust everyone to make their best effort with the information they had at hand, we don’t blame people when things go wrong but everyone does jump on board when trying to fix something.
Tyro is a unique environment. It is a disruptor in the marketplace and it is an innovator on the testing front. Whilst most banks favour, formality, and heavy weight process and artifact based testing, Tyro aims to produce the best work available through activity. Working alongside developers, questioning the product, looking for leanness and efficiency, adding value and bringing a context driven approach to testing. It has not been an easy road. It has taken alot of encouragement (via coaching) to produce good testers (and in some cases, outstanding testers) with the courage to create, innovate and articulate their own methods.
For the ANZAC day long weekend, I decided to ride my motorbike down to Melbourne. Why, I hear you ask? To see how hard it it would be, I reply. My partner woke me up at 5am on the Saturday because he was flying down there. He didn’t want to sit on the back of a bike for that long – fair enough, I say. For me it was about the journey and not the destination. I have more fun with corners on my own anyway. So I got up at 5, this was after staying out till 1am the previous night singing karaoke with my boss on her final day at work and after an injury on Thursday which made me think I wouldn’t be able to ride to Melbourne. Oh and I had developed a mild cold.
Melbourne is nearly 900km from Sydney
I thought, “fuck it, let’s see how far I can get, I don’t have to get to Melbourne”. So by 7am I had packed my camping gear, food, clothing and winter riding gear and was on the road. My first stop was in Menangle.
I was freezing by this point and really needed to go to the toilet and I was only 40 minutes into my trip. I stopped at a rest stop and was very glad I had packed my winter gear. I pulled out the winter gear, lined my jacket and put on my thick riding gloves. Then back on the road.
With the camping gear on the back, I had to be more delicate with the way I got on my bike, I had to step on the foot rest, balance my weight and get my right leg over the luggage. I was concerned it would fall over while my leg was halfway over but it never did. Getting off was the same process but in reverse. Curbs and flat roads were my friends for this trip.
I was still getting cold from the airflow coming up from under my helmet, I didn’t have a scarf, there was much sadness until I thought I could use my spare shirt as a scarf. Genius. The only problem that was plaguing me now was an insistently runny nose. Let me tell you, you do not want to sneeze inside a helmet with the visor down. Not a pretty sight. I did not have any way to blow my nose either. The only thing I could think to use was to wipe my nose with my glove. Gross.
I ducked into a maccas along the way for breakfast, I believe now that Maccas and fuel stops are the main source of work along highways. I swear I saw a maccas every 50km and a few times I saw two facing each other off, one for each direction of traffic.
My first fuel stop was in Yass around 11 am, just north of Canberra. Yass is a quant thriving highway town, I browsed a few shops and had a coffee. I thought I was making great time and I thought I’d be in Melbourne by 6pm.
The next leg of the trip was challenging, when I was a 100km away from Albury my left hip started to cramp up around 1:30. I pulled over, walked around a bit and it seemed to go away. Got back on the bike and I thought it was ok but it started to cramp back up in 10 minutes. I tried not to move it at all but I think that made it worse. I was thinking I wouldn’t make it to Melbourne, I was thinking I should just get to Albury and find a camping spot there. I think the last 100km to Albury was the most challenging part of the Journey.
I arrived in Albury around 3:30 and I had to fill up again, as I got off and walked around, I thought, “I’ve made it this far, Melbourne is only a few extra hours away”. My new eta in Melbourne was 8pm. I had a new strategy for the cramped hip, lots of movement. I was standing on the bike, doing bike squats and bike squat butterflies. A bike squat butterfly is where you raise your bum off the bike seat a little and move your legs out and in quickly. I don’t know what else to call them. I filled up fuel again in Seymour around 6pm and actually arrived in Melbourne by 7:30 pm but it took me 20 minutes to get through the CBD to chinatown where I was meeting my partner and a friend.
Turns out, I had parked my bike almost directly outside my partners hotel room without even knowing where he was staying. We hadn’t coordinated this and it was great how it just happened. We had Yumcha and I was exhausted. It took me the better part of 12.5 hours but I had done it, I had ridden to Melbourne in a day.