Louise Gibbs
Senior Automation Tester
I am Open to Write, Teach, Speak, Mentor
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.
Achievements
Certificates
Awarded for:
Achieving one or more Community Stars in five or more unique months
Activity
achieved:
This badge is awarded to members who update their profile with a new photo.
achieved:
This badge is awarded to members who visit the Ministry of Testing site 404 times
achieved:
This badge is awarded to members who visit the Ministry of Testing site 99 times
achieved:
This badge is awarded to members who update their social links on their profile.
achieved:
This badge is awarded to members who indicate they are open to work, writing, teaching, speaking, mentoring, CV reviewing or internships.
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...
This means a ticket must NOT be marked as done until the automation work, as well as development and manual testing activities is completed
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.
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.
First day of 99 Second Talks at TestBash Brighton 2024
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,...
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 ...
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts.
Learn about the variables in SpecFlow
Learn how to set up bindings in SpecFlow
Experiment with products using different accessibility tools
Watch Louise Gibbs' Experience Report on Web UI Automation from Test.bash('Online'): 2020
