Showing posts with label learning. Show all posts
Showing posts with label learning. Show all posts

Wednesday, 29 June 2016

#ltgworkshops competition winner - Erik Hörömpöli's blog post

A short while ago there was a competition to win a ticket to #ltgworkshops 2016.

As part of the competition if you won you had to write a blog post about your #ltgworkshops experience. 

Erik Hörömpöli was one of the winners. Erik has a blog which you should check out.

I've replicated his blog post here.

I’m still pretty new to the scene of software testing conferences, only went to my first ones this year. I was so curious already, that I paid everything for myself just to go to the first #EuroTestConf and the #CopenhagenContext. Amazingly, my next conference was through winning a competition by Tony Bruce (http://dancedwiththesoftware.blogspot.hu/2016/01/london-tester-gathering-workshops.html).
By going to London I was in for a different kind of conferring. London Tester Gathering Workshop (https://skillsmatter.com/conferences/7219-london-tester-gathering-workshops-2016) is organized by Tony and his friends at Skills Matter and solely built upon hands-on workshops and discussions with practical exercises . Sounds great, huh? Not only sounds.
Skills Matter/Code Node venue fits very well for such an event, with easy orientation and different sized rooms. Before the sessions we raised our hands saying which sessions we want to go to and were distributed easily. And they have cool people as staff! I was approached by at least three of them during the two-day event asking about testing or feedback for the event/venue.
For the first day I choose Mark Winteringham’s full-day workshop about web services which I’ve worked previously only a bit before and my current team just created the first API for the part we are working on, so this tutorial couldn’t come at a better time. Mark started out with the basics, explains through his slides (http://mwtestconsultancy.co.uk/presentations/understanding_web_services/) what he thinks important to mention about web services (that you can think about it as a machine-to-machine communication), walked through his well thought-out exercise (he acts as a product owner for a booking site’s service), we practiced the main types of requests (post, get, put, delete), talked about context (we can try many things here, but what should we?), fired up Postman and Blurp and discussed it’s strengths and weaknesses (Postman doesn’t “save” your response, you need to send your request again – can be annoying if you want to remember or later compare two responses), learned about how to use cookies and saw Mark handling well his unreachable environment. Later in the afternoon we heard about why a service is restful and paired up for practicing modelling to aid our testing.
2016_06_24_15_01_56_London_Tester_Gathering_Workshops._Flickr_Photo_Sharing_
(ALL PHOTOS: HTTPS://SKILLSMATTER.COM/CONFERENCES/7219-LONDON-TESTER-GATHERING-WORKSHOPS-2016#PHOTOS)
Much of this is for later practice, as it happens often on a conference, being there is great to have the information or contact persons who you can go to (do I need to introduce the https://testersio.slack.com/? You can chat with Mark there among other smart and kind people), have the resources and the inspiration to learn, share and lead.
I already experienced before that the talks worth the least of your time on a conference. If nothing else, stay out on the hallway and talk to someone or play an educating game. This just got reinforced by attending workshop-type conferring. They give you the kind of knowledge you think you will get when you sign up for a talk and gets you into the working and professional mood as a lean coffee formatted session.
An even more romantic interlude: it can happen to you that you are afraid of such a workshop/conference, because you lack (or you think you lack, compare to others!) certain technical skills or you are shy, but I can only hope that you will do the first step to come out of that, because immediately at the second step you will see that the world-wide testing community is a very safe-to-fail zone and you share the same kind of problems, worries and wins with many.
Probably not the most interesting part of such posts are the chronological story of what happened on the workshops, so I’ll  try to save you from much more, but I really enjoyed Maria Kedemo’s testability workshop (which I was looking forward after her CAST talk on the very subject: https://www.youtube.com/watch?v=_VR8naRfzK8), where we worked with two simple and powerful definitions (testing=gaining information, testability=how easy is something to test), fought over having the box that were handed to the teams (hence, availability is part of testability) and thanks to Stephan’s (https://twitter.com/S_2K) smart remark we realized we like to blame project circumstances more than ourselves when it comes to testability after we put our sticky notes with our pain points on them on Maria’s and Ben Kelly’s ever-evolving model (http://testjutsu.com/2016/06/dimensions-of-testability/ – by putting much of that on the Project and not on the Tester side). The day ended with an ultra-social session by Dan Ashby and Tony himself where we muscled ourselves through the possible definitions of coaching, mentoring and teaching (was there a fourth one?), practiced active listening and teamwork through games. We call them soft skills, but remember that they are harder to learn!
Here is a link (http://dancedwiththesoftware.blogspot.hu/2016/06/presentations-and-materials-from-london.html) to Tony’s post where you will find all the resources that has been shared by facilitators this year. This event almost made London look like a warm and welcoming place!

Friday, 20 November 2015

A BDD lesson from my past - Part One

So, a few years ago I was involved in an agile transformation.
I was part of the consultancy brought in to work with a client.
As part of our learning through trial and error, we decided to try Behaviour Driven Development.
I wanted to learn from what we went through and share it with others.
I also wanted to learn what some of the people on the client site learned.
I worked with two separate people and we came up with 2 talks.
We worked with the same theme but taking their different experiences and personalities we created different talks.
It worked quite well.
Thanks to @andrewjutton and @brightoniant for joining me on this exercise and also being willing to go through their first presentation experience with me.
Recently @friendlytester wrote a post which reminded me of that time.
His post prompted me to write this post.
Are you sitting comfortably? Good. Then we'll begin.

Many moons ago, a few people came across SpecFlow and this lead them to Behaviour Driven Development.
We didn't spend time thinking through exactly what we wanted to achieve, or how we'd know if we were getting there.
SpecFlow, however, was shiny and new and we were still working on how exactly we were going to use automation in testing. 
We were lucky that people with the business knowledge were available.
We were unlucky in that the people with business knowledge were offsite most of the time.
We decided to trial BDD, which was driven by the tool and by the 'Software makers', which at the time did not include anybody from the business.
This (now) seems wrong and didn't work as effectively as it could have.
I have no evidence to back this up, but I believe that having the business suggest the idea of BDD would change the approach completely. 
BDD is about focusing on collaboration, not focusing on a tool.
You can work with BDD without ever using automation and receive plenty of value.
In-some cases you'll be better off as you won't get lost in the tool and focus on the collaboration.
Collaboration is the key and point.

So, there we were; Giving it, Whening it and Thening like mad.
Mostly written (solely) by the Business Analysts and therefore bypassing a shared understanding and attempting to share one person's understanding.
Here's an example:
Scenario: Display ‘Insurer Selection’ screen

Given that Insurer selection screen has been invoked
When the Insurer selection UI is rendered
Then the ‘Insurer Selection’ page is displayed
And the ‘Risk Variation Name’ field is displayed
And the ‘Risk Variation Name’ field is selected
And the ‘Customer Name’ is displayed
And only breadcrumb ‘Select Insurer’ is displayed
And all insurers setup in the system for the policy type are displayed
And all insurers setup in the system for the policy type are not selected
And the ‘Next’ button is disabled
We were learning.
We hadn't quite grasped yet that the how wasn't important, it's the what that is important.
What is actually trying to be completed?
End of part one.

Thursday, 23 July 2015

London Tester Gathering Workshops 2016 - Call for thoughts

The London Tester Gathering Workshops bring together some of the greatest minds in our industry, to learn, share and evolve the tool and techniques that matter to you! A joining of 100+ testers, #LTGWorkshops creates an unrivalled space for meeting fellow testers facing the same engineering problems. At the centre of the conference is a tried-and-true design with a focus on giving you the advantages you won't find in the manual!
Join us at #LTGWorkshops on the 2-3rd of June 2016! Come along to discover and learn good ideas and techniques in testing. At the end of these two days, you will know how to use modern testing practices and provide the information your stakeholders need to make informed decisions.
WARNING - This is not your event if you want to sit and listen. This is your event if you want to discuss, learn, share and do.
All Skills Matter’s conferences are crafted with the community in mind; for people who are passionate about discovering and learning innovative approaches and technologies to crack the engineering challenges in our industry. People like you!
We hope you can help us organise a valuable event that helps you discover and explore those ideas, technologies and practices you need, featuring the experts you want to learn from and formats that best suit you, by sharing your ideas in this Call for Thoughts.

Monday, 20 July 2015

Are you coming to Agile Testing Days 2015? Will a 15% discount code help?

Want to come to Agile Testing Days 2015? Will a 15% discount code help?

Embracing Agile for a Competitive Edge - Establish leadership by delivering early, rapid & iterative application releases” is the Motto of this Year’s Agile Testing Days. We proudly present the 7th edition of Europe’s greatest agile event of the year!

Check out the program here.

Check out last year's.


15% Speaker Discount Code: TonBru_015
The code is combinable with other speaker codes!!

Thursday, 19 June 2014

Black Ops Testing Webinar Alert: Monday June 23rd 20:00 BST


What would challenge us?

Something small, but something large?
Something remote, but something local?

We picked TodoMVC.
Don't know it?
Have a look.

It's not really a production application. It's a showcase application.
That means, the same basic functionality written in lots of different frameworks.

Our challenge - "Have a look and see what you come up with"
And now we debrief.

Save the date Monday 23rd June, 20:00 BST

You can sign up for the webinar here 

And for maximum value, have a look at TodoMVC yourself before you attend.

Friday, 11 April 2014

Join the Black Ops Testing Webinar - 14th April

Our first Black Ops Testing webinar takes place on the 14th April.


We added a 'stealth mode' to our Newsletter signup on the front page of our website.

For our first webinar, we will debrief live with our thoughts on how we would test this, and work around this.

Using techniques and thought processes that we will cover in detail on our 2 day workshop, we will discuss the challenge of our 'Stealth mode' signup.

Expect us to:


  • share tips about proxies 
  • discuss in-browser development tools 
  • css tricks and tips 
  • mock each other for not trying techniques 
  • deliberately say or do something wrong - 'live' 
  • We plan to have fun for 30 minutes, and we hope to learn from each other.


Join us, and take part in the chat live.

If you take the stealth challenge before you attend then you can tell us what you found in the chat and we'll include you in the discussions.

Sign up for the webinar. It takes place on the Monday, the 14th of April, at 20:00 (GMT+01). If you register your interest and can't make it, then we may have a replay available.

Friday, 14 June 2013

Weeknight Testing: Is ATDD perceived to be the next silver bullet?

The next Weeknight testing session is on the 19th June at Skillsmatter
We will hold a workshop to demonstrate:
  • why software investigation is needed even if you have acceptance criteria.
  • the difference between checking off acceptance criteria and investigating the software with exploratory testing sessions.
  • how you can strengthen your acceptance criteria checks with information gathered through exploratory testing sessions.
Bring a laptop.

Register here

Monday, 22 April 2013

I went to Mile High Agile 2013 and I liked it.

I went to Mile High Agile 2013 and I had a interesting time.

The Keynote was from Joe Justice who spread the word about Team Wikispeed: building a 100 MPG car using Agile & Lean methods
You get the drift of the talk from the title, it was great to see how far they've come using these methods and also how they are able to help others using the methods.

The Keynote was filmed but I don't know what happens with the recording, whether or not it's put online for public viewing.

Find out more about wikispeed.

I managed to catch Paul Rayner's DDD Workshop which I enjoyed.  I think it gave a good introduction and a few take aways to think about.

We worked through a exercise and we were working out our domain model.  I won't write down too much detail as I don't want to give it all away.




Paul's was the only session I managed to catch as I spent a lot of the day in the coaches clinic.

The coaches clinic is a great idea and the basic setup is that people can drop by a booth and book in some time with a coach to talk about about pretty much anything agile related.

Whether it is issues they are experiencing or things they are unsure of and so on.

I enjoyed the clinic and it was interesting to talk with people who needed help with some different areas.  I hope I was able to help with some things to take away and think about.

Some of the things we discussed ranged from whether or not to use Scrum or Kanban to how to get more out of Product Owners. 

While I didn't make many of the conference talks I definitely feel my time was well spent.

My thanks to Pete Behrens for inviting me to be a part of the clinic.

My own talk was at the end of the day and it was still a pretty full room which I was surprised about purely because usually some people have left by the last talk.


My talk was about Change and the Prezi is available.

I caught a glimpse of the feed back forms and it was a mixed bag which is pretty good, in my experience it's hard to have a talk that is going to reach everybody the same way.


I do wish that the people who didn't get much out of talks would offer more feedback.  It seemed like the people who got something out of the talk offered comments and the people who didn't just marked down a score and left it at that.
That makes it very hard to improve.

All in all a good day, had a lot of different conversations, hopefully gave some people some things to think about in both the clinic and my talk and met a lot of really dedicated people.

My thanks to agile Denver and all the volunteers for bringing me along for the ride.


After the conference I got to meet Lisa Crispin's donkeys , Ernst and Chester.

Matt Barcomb was also Lisa's guest and it was great to be able to spend time with Matt, Lisa, Bob (Lisa's husband) and Lisa and Bob's extended animal family.

It was great to meet Matt and I'm looking forward to his (and Jim Holmes's) session at Eurostar.

My thanks to Lisa and Bob for inviting us (my wife and me) over. They are fantastic hosts and we had a great time.


 Matt and Lisa
My wife Marisol




Monday, 8 April 2013

Explaining testing: 101 Tactics For Revolutionaries

Here are the first 10 to get you started.

Onward to glory!

  1. if you’re in charge, do it yourself
  2. if you’re not in charge, do it yourself
  3. become known as “the guy who…” so when the time is right, everyone knows there’s a guy who…
  4. learn to be nice, so people like you
  5. realise there are no rules, you can do what you like
  6. know that you are as right as you can be for now given what you’ve learnt so far
  7. know that this is the same for everybody else
  8. stay on the inside of the wrong thing so you can speak with authority on why and how it is wrong
  9. know it’s not a race. That you can divide the world into those ahead of you and those behind, and to all those ahead of you, you’re the one behind.
  10. be an entrepreneur not a crusader
The rest are here: 101 Tactics For Revolutionaries

Sunday, 10 March 2013

Inbetween talks - Agile Dev Practices 2013


So #agiledevprac has been and gone.

I had a great time.


During the Monday my fellow speaker Ant and I had a chance to hang out with Maik Nogens.

Maik's a great guy, if you see him (you can't miss him, he's 8ft tall, although everybody looks 8ft tall when they are standing next to me) say hi.

We had a walk around Potsdam and sampled a couple of Bratwurst.  This is my second time in Potsdam and I think it's a great place, nice, quiet and picturesque.

On the first night there was a speakers dinner at Walhalla.

Jose stood up and gave a short speech welcoming everybody.

The food itself was OK, the company was great.

Ant and I had both chosen a fish dish which came with bacon sauce. BACON. SAUCE. How could you not?!

We'd been waiting and looking forward to it for weeks. We'd been imaging all sorts of amazing creations.

It was one of the biggest disappointments ever. It is a cream sauce with bits of bacon in it.



Ant and I shared a table with a number of people and we spent the most time talking to Ray Scott and Vagif Abilov.

I've come across Ray and Vagif before in my travels but have never had a chance to sit down and have a proper talk.

It was great to do so.

After dinner there was a short visit to the hotel bar and then off to sleep.


Over the next few days there were:

  • Pop-up coding dojos.

  • Conversations all around with people from the world over.
    • I would love to list the names of everybody I had a conversation with but there are too many.
  • Ant drank his first ever full pint of beer, followed by his second, and third, etc.
 
  • A social dinner event complete with improv comedy troupe.
    • Ant and I were on the same table and again had a number of diners with us. During dinner we spoke mostly with Ray Scott and Krystian Kaczor
    • After the meal we spoke with a few more people.
  • A group of us went for a meal, sat down and realised none of us speak German.
    • We had 2 English guys, 1 Hungarian, 2 Spanish guys and 3 Russians.
    • Luckily, one of the waiters spoke Russian so we were able to get a meal organised.
Unfortunately I didn't get the names of two of the (Russian) guys at dinner, the rest are:



It was great to catch up with some people, meet new people, have some great meals and have some great discussions.


In my opinion, over the next few days there were some good talks, some OK talks and some talks that didn't quite work.

Conferences are essentially a meeting of people who want to contribute, teach, learn and share.

It's not just attending the talks.

Make the effort to meet new people and talk and you will get untold value from a conference.

Wednesday, 30 January 2013

Total awareness of conditioning

How do I free myself from my conditioning of the culture in which I was born? First, I must be aware that I am conditioned; not somebody telling me that I am conditioned. You understand the difference?

If somebody tells me I am hungry, that’s something different from actually being hungry. So I must be aware of my conditioning, which means, I must be aware of it not only superficially, but at the deeper levels. That is, I must be aware totally.

To be so aware, means that I am not trying to go beyond the conditioning, not trying to be free of the conditioning. I must see it as it actually is, not bring in another element, such as wanting to be free of it, because that is an escape from actuality. I must be aware. What does that mean?

To be aware of my conditioning totally, not partially, means my mind must be highly sensitive, mustn’t it? Otherwise, I can’t be aware.

To be sensitive means to observe everything very, very closely; the colours, the quality of people, all the things around me. I must also be aware of what actually is without any choice. Can you do that?

Not trying to interpret it, not trying to change it, not trying to go beyond it or trying to be free of it; just to be totally aware of it?

Jiddu Krishnamurti - The Awakening of Intelligence

Sunday, 27 January 2013

Why would I need excuses?

Recently uTest posted "8 Common Excuses in Software Testing" and within the comments there was a link to "Excuses for testers when bugs are caught in later testing cycles/UAT/Production".

My immediate thought was 'WTF? Why would I need excuses?'.

Reasons, yes, explanations, yes, but excuses? Hell no.

Am I wrong? Do I need excuses?

Or am I getting reasons and excuses mixed up?  Are some people taking them to mean the same thing?

At the end of "Excuses for testers when bugs are caught in later testing cycles/UAT/Production".  There is this sentence 'Well these are not actually excuses. These can be the actual reasons why an application is shipped to client with major bugs.'

The way I understand the two in this context are:

Reasons
1.a basis or cause, as for some belief, action, fact, event, etc.: the reason for declaring war. 
2.a statement presented in justification or explanation of a belief or action.

Excuses
1.to regard or judge with forgiveness or indulgence; pardon or forgive; overlook (a fault, error, etc.): Excuse his bad manners. 
2.to offer an apology for; seek to remove the blame of: He excused his absence by saying that he was ill. 
3.to serve as an apology or justification for; justify: Ignorance of the law excuses no one.

I am not a gate keeper, I am an information provider, I have limited time to provide what information I can.

I will do my best, the people around me will do their best and sometimes we will not be able to investigate everything.

I'm happy to explain things but make up excuses?  I think that will do more harm than good.

There are plenty of reasons why issues end up in production, learn from them, explain, improve how you test and what you test.

Don't make excuses.


28/01/13 Update.
Forgot to add, what and how you are testing and what you are not testing should be communicated and continuously communicated as you delve deeper into the software.

Thursday, 10 January 2013

Weeknight Testing....BRB..

So a while back a bunch of clever people started this thing called Weekend Testing

About us
WT formerly known as Bangalore Weekend Testers is the acronym for Weekend Testers. We are a group of testers who have synergy towards testing software and learning from it. We also belong to the group of testers whose vision is to improve the craft. We are bringing Weekend Testing through our first chapter – Bangalore Weekend Testers, to find people with similar synergy.
Mission of WT
A platform for software testers to collaborate, test various kinds of software, foster hope, gain peer recognition, and be of value to the community.
You should already be aware of it, if not, look into it. Good times.
 
And out of it grew Weeknight Testing.

Weeknight Testing slowed down as we all got busy with life and there hasn't been a session for quite while.

Sharath has been in contact and we're looking at reviving it.

If there is anything you would like covered or if you're interested in running a session let us know.

I think (tbc) we're going to be looking at running it in different ways, not sure exactly yet but I think we'll mix between in person and on-line sessions.

Details on a couple of past sessions:

WNT – Black Box Security Testing

Week Night Testing: Requirements analysis & testing traps

Weeknight Testing #04 – an experience report

Agile Testing UK:Weeknight Testing Live 


  - Live video streamed between Germany, San Francisco and London.

Get involved.


Test. Learn. Contribute.


Cheers

Tony.

Tuesday, 2 October 2012

I'm supposed to be negative?

So I've overheard recently  (over the last year or so) things like: 'It gets tiring being negative all the time and pointing mistakes and people flaws.'

And it confused me.

Is that what I'm supposed to be doing?!

Crap!

I've been doing it wrong!

Should I be negative?

Should I be pointing out flaws in peoples work?

Should I be pointing out flaws in peoples ideas?

Should I be stating that people are doing shoddy work?

Am I there to break things?

Am I there to find the breaks?

I thought I was part of a team and we worked together on creating something.

I thought I approached things differently and could add valuable input because of that.

I thought we were solving a problem and approaching it from different angles.

I thought I was there to provide information.

I thought  we evolved together.

Did I think wrong?