Louise Gibbs
Louise Gibbs
Senior Automation Tester
Louise is a Senior Automation Tester at PebblePad. Her main job is to review and maintain the automated tests that are run overnight, and investigate the causes of any failures. She has also worked for companies in the e-commerce, scientific research and automotive industries, and runs a personal blog at louisegibbstest.wordpress.com, where she talks about her experiences as a software tester. She enjoys improving her testing skills and her main method for achieving this is by speaking to other Testers and discussing ideas.
🎂 MoTaBirthday | August 1, 2018
Open To
Write
Teach
Speak
Mentor
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...
18 Aug
4 Photobooth Images from TestBash 2024
This attendee wears a pink Ministry of Testing shirt with a lanyard, and in each photo, their poses are varied. This attendee has Medium length brown hair,...
20 Sep
A group of several people kneeling and standing up on a conference stage. There is a woman at the front taking a selfie. Most people wear pink t-shirts with a Ministry of Testing logo. Most people ...
18 Sep
Learn how to get started with SpecFlow and create your first UI automation test with Louise Gibbs
18 Feb
First day of 99 Second Talks at TestBash Brighton 2024
1 Oct
Flaky Test
A test that passes in one run and fails in another — with zero changes to the code, the environment, or the test itself.That non-determinism is what makes it flaky. It's unreliable not because the application changed, but because something about the test is inherently unstable — a race condition, a timing dependency, reliance on external state, etc.Calling a test "flaky" just because it caught a bug muddies the conversation and, worse, can lead teams to dismiss legitimate test failures.
Smoke testing
Smoke testing covers all areas of the software application without getting too deep. We decide which features to test. The goal is only to check they are working, not exhaustively test these features. Smoke tests need to be repeatable.
Mutation testing
I see mutation testing as a process for thoroughly testing our tests to ensure that we can really rely on them. My recommendation is to do mutation testing every time you create or edit a test. You should also review your automated tests making sure it is still relevant. You should do this regularly. You'll need to make sure that tests keeps up to datewith changes to the software. My process for mutation testing involves going through all the steps of a test and listing all the ways each individual step could fail. I then attempt to simulate these failures by either changing the state of the software before the test is run, running the test in debug mode, and then pausing the test using breakpoints to try and simulate a failure, changing the software at that point, or adjusting the test code itself to check the accuracy. Another reason I find mutation testing useful is because it allows me to design the tests to give useful messages if certain failures have occurred.
Exploring the Impact of AI on Workplace Collaboration: Survey
(louisegibbstest.wordpress.com)
12 Dec 25
Test Automation As You Go: Redefining The Definition Of Done For Quality Software
(louisegibbstest.wordpress.com)
04 Apr 25
Not registered for any upcoming events
Observatory Enabler
This badge is awarded to those tagged in their first Observatory link.
Badge Award
4 days ago
Moment-um Builder
This badge is awarded to those that have been tagged in their first Moment.
Badge Award
4 days ago
Contributed to a Session
99 Second Talks - Day 1 at TestBash Brighton 2024
Community Star
about 2 months ago
Learner completed your lesson
16.3.0 of MoT Software Testing Essentials Certificate
Community Star
about 2 months ago
