Lewis Prescott
Lewis Prescott
QA Lead
I am Open to Give CV/Resume Feedback, Mentor, Teach, Write, Speak
I'm an experienced QA Lead at IBM, book author. I am also a course author on Test Automation University, sharing my knowledge is a passion of mine.

Achievements

Career Champion
Club Explorer
Bio Builder
Avid Reader
TestBash Trailblazer
TestBash Speaker
Glossary Contributor
Cert Shaper

Contributions

Quality people. image
  • Aj Wilson's profile
  • Lewis Prescott's profile
  • James Wadley's profile
  • Geir Gulbrandsen's profile
  • Jesse Berkeley's profile
  • Nataliia Burmei's profile
Happy times gathering again at MoT London with these quality people.
 Recording in action: Lewis Prescott on Contract Testing – Coming soon! image
  • Lewis Prescott's profile
Here is Lewis Prescott, recording a lesson for his upcoming course, "Modern integration testing: Tools, techniques, and strategies for continuous quality." In this lesson, Lewis walks you throug...
Zero bug policy image
  • Lewis Prescott's profile
The premise of zero bug policy is to redefine what is classified as a bug. Peter Hilton explains that the aim of the zero bug policy is to fix bugs before adding any new code. Switching gears frequently to fix bugs and test the new code can lead to unpredictable development timelines, which a zero bug policy can help to address. Within my company, bugs are called “live issues” and are immediately documented as user stories. This means that they get prioritised alongside all other user stories, so they carry the same value (in theory). So bugs are categorised as follows:  Bug found in production -> “Live issue” created as user story  Bug found during feature testing  Must be fixed before release -> User story, prioritised for development and testing  Feature will be released with bug present -> User story for that feature is updated to account for bug  Bug found during regression  Must be fixed -> User story created and added to backlog  Satisfied with existing workaround -> No new user story created  Bugs found during regression testing can point to a gap in testing: for example, tests were not updated when some requirements were changed. These, too, are categorised as user stories and can be prioritised accordingly.
Tech and Testing Debt image
  • Lewis Prescott's profile
  • Veerle Verhagen's profile
I tuned into a conversation on testing debt for STEC with Veerle Verhagen and Lewis Prescott What a wonderful conversation covering so many aspects of testing debt: - What factors influence how...
Pact Nirvana with Lewis Prescott and Marie Drake image
  • Lewis Prescott's profile
  • Marie Cruz's profile
We talk about pact nirvana and how to achieve it, celebrating small wins, benefits of contract testing, enabling developers to test with modern tools and managing contracts at scale with Pactflow.
First ever London Ministry of testing Meetup - Diana + Lewis + Rafa image
  • Diana Dromey's profile
  • Lewis Prescott's profile
  • Rafaela Azevedo's profile
diana, lewis prescott and rafaela azevedo. First london meetup
MoT Software Testing Essentials Certificate image
  • Simon Tomes's profile
  • Sarah Deery's profile
  • Ady Stokes's profile
  • Rosie Sherry's profile
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.
Learning To Lead Before Becoming a Leader image
  • Lewis Prescott's profile
How to engineer situations to develop your people management skills
Zero Bug Policy: The Myths And The Reality image
  • Lewis Prescott's profile
Lewis shares his experience of working with a Zero Bug policy. What is it, how does it work and how can it help?
The Most Awesome User-focused Dashboard image
  • Lewis Prescott's profile
Put your users front and centre with this team activity
Login or sign up to create your own MoT page.
Subscribe to our newsletter
We'll keep you up to date on all the testing trends.