Nicola Lindgren
Quality Engineering Manager
I'm Nicola , a Quality Engineering Manager based in Malmö, Sweden. I'm constantly looking for ways to learn, grow and adapt.
In the past, I have worked on projects in various industries including Education, Retail and e-Commerce.I was the founder of the Stockholm Software Testing Talks meet-up and a co-founder of the WeTest Auckland testing meet-up. I was also a frequent co-instructor for the BBST Foundations course. If you want to read my thoughts on software testing, feel free to check out my blog: https://nicolalindgren.com
Achievements
Certificates
Awarded for:
Achieving one or more Community Stars in five or more unique months
Activity
earned:
5.2.0 of MoT Software Testing Essentials Certificate
earned:
Member visited How Can I Test This?
earned:
2.4.0 of MoT Software Testing Essentials Certificate
earned:
2.3.0 of MoT Software Testing Essentials Certificate
earned:
8.6.0 of MoT Software Testing Essentials Certificate
Contributions
Eighteen months, 19 modules, and 59 amazing contributors later, the MoT Software Testing Essentials Certification is complete!
Looking back, my favourite part has been seeing so many community m...
Hello, my name is Emily!
I’m travelling to TestBash from Leeds (UK) and I’d love to meet and form stronger relationships with others who are senior individual contributors.
I'd love to get to k...
Examples of how to test different sites and apps, along with the test heuristics applied, the reasoning and tool ideas. Nicola Lindgren, Mike Harris, Suman Bala, Philip Wong, and Shawn Shaligram
A guide to finding your first role as a Software Tester, upskilling so you are relevant in the job market and succeeding as a Software Tester once you have landed a role.
I share some examples of what a typical day might look like for a software tester.
[When it comes to testability] I've found that any requirement that needs involvement from another team is a hassle to test. You have to align with other teams. That is an extra potential problem. I tend to watch out for those requirements.
two people suggest you fix flaky tests by disabling them or doing a retry. someone else suggests you automate at right layer, use appropriate waits and better selectors
Meme about technical debt. holding teams back from adding new features
