Skip to main content

About Nicola

Hej!

I'm Nicola Lindgren (née Owen), a New Zealander living in Malmö, Sweden.

As a tester I’m constantly looking for ways to grow and learn; whether that be through taking courses, reading blogs or bouncing ideas off people I look up to in the field. 

If you want to find out more about me check out my LinkedIn Profile or follow me on Twitter.

This blog is an attempt to document my learning journey. As I write this blog, I'm sure that my opinions on testing will develop and change. I'm learning, exploring and seeing what's out there.

I'm keen to explore and understand new/different ideas about testing - feel free to reach out to me on deament @ gmail dot com

When I'm not testing you'll find me playing board games and running/gymming sporadically (still working on building that habit).


Past Talks and Workshops 

EC Utbildning - Online - December 2020
Life as a Tester 

Guest Webinar with TestCraft - Online - October 2020
Learning to ask for testability

SAST Öresund Q2 Mötet - Malmö, Sweden - 15 May, 2019
Learning to ask for testability

TestBash Essentials - Brighton, UK - April 3, 2019
Learning to ask for testability

ThinkTest - Lund, Sweden - March 21, 2019
Reducing the fear of go-live

ScanAgile - Helsinki, Finland - March 14-15, 2019
Bringing in change when you don't have a leadership title

Agile Testing Days - Potsdam, Germany - November 11-16, 2018
Bringing in change when you don't have a leadership title

Belgrade Test Conference - Belgrade, Serbia - November 7-8, 2018
What I wish I knew in my first year of testing

House of Test Conference - Malmö, Sweden - 26 May 2018
Reducing the fear of go-live

Oredev 2017 - Malmö, Sweden - November 8-10, 2017
Reducing the fear of go-live

TestBash Belfast 2017 - Belfast, Ireland - May 18, 2017
Testing so you can move on

Romanian Testing Days 2017 - Cluj, Romania - May 10-12, 2017
Testing so you can move on

EuroSTAR 2016 - Stockholm, Sweden - November 1-3, 2016
What I wish I knew in  my first year of Testing

Session Based Test Management - October 25-26 2016
I was the co-presenter of a 2 day workshop at Unity 

Let's Test 2016 - Stockholm, Sweden - May 23-25, 2016
The Art of Picking Your Battles

TestBash 2016 - Brighton, UK - March 10-11, 2016
Nowhere to Hide: Adjusting to Being a Team’s Sole Tester

EC Utbildning - Malmö, Sweden - September 2015
Life as a Tester 

WeTest Auckland Meetup - Auckland, New Zealand - July 2014
Bug Advocacy: How to do a great job reporting and managing bugs



Comments

Popular posts from this blog

A reflection on Let's Test 2015: Part II

Here's the link to A reflection on Let's Test 2015: Part I The sessions (Part II) Below does not include all of the sessions I went to nor all aspects of the session I mention Visual Creativity: Using Sketchnotes and Mindmaps to aid your agile testing - Dan Ashby and Christina Ohanian Before this session I stumbled upon Christina drawing out her sketch notes from the previous session and marvelled at how fascinating it was. Sketch notes were only something I'd only ever seen on the net. They were gorgeous and a clever way to communicate information. When she told me that she was going to have a session on this - I was all in. We 'warmed up' by drawing whichever image came to mind when Dan said a word. It was interesting to see how a lot of people could interpret the same word differently. For example: "Time" could be a clock, a watch or an hourglass.

Getting started on a testing project

I started on a new project a few weeks ago and thought it would be a good idea to share a checklist for what new testers on a project need and some good starting questions when you, as a tester, are new on a project Checklist for what new testers on a project need (Note, your project may not include all of the below) Note to check if user credentials are needed for any of the below

My Most Used Test Heuristics (with examples)

First, what is a heuristic? A heuristic is a guideline ,  it is fallible.  Therefore, it will give you a good idea of what behaviour you should see BUT it isn't definitely what should happen - it's up to you to confirm that the behaviour you are seeing is correct.  In a previous blog post I shared a step by step guide on  how to test without requirements/little requirements.    But I figured it's good to share my most used test heuristics that I use for testing without requirements. They are: Consistency with History Consistency with User Expectations Consistency within Product Let's take a look at each of them along with some examples to illustrate the concept. 1. Consistency with History  The feature's or function's current behaviour should be consistent with its past behaviour, assuming there is no good reason for it to change. This heuristic is especially useful when testing a new version of an existing program. (Source: developsense) Example: Whitcoulls, a