I'm Lewis Prescott and I am currently a QA Engineer at Asos, formerly of 'The Test People' based in the Leeds office. I have a variety of experience at different organisations, usually forming opinions on automation and the best way to adopt it. I currently love writing unit tests and getting involved in testability discussions with my colleagues. I teach coding (python) at a local school in Camden, London. I mentor an intern and another QA here at ASOS. I love to teach and learn from others. Asos is a large organisation which has grown significantly over the past few years. This had meant layers of management and teams spawning out of nowhere. I want to discuss my journey of implementing Pact (Contract Testing Framework) in a large organisation. The challenges I faced during the process and the lessons learnt including the technical Part: Setting up the framework in C#, people part: Getting buy in from the wider team and consumers part: Gettting buy in from the wider business.

This talk builds on my course for Test Automation University (https://testautomationu.applitools.com/javascript-api-testing/) Using the power of mocking and the tool Nock. You can build component and integration tests with one set of scripts. I will show you how this is possible and also explain the difference between component and integration tests. In order to make your tests fast and build tests at the right level, use the power of mocking. The JS Monthly Meetup was organised by Aris Markogiannakis (JS Monthly host) and hosted by Prisma. ✨ Join the Prisma Meetup group here: https://www.meetup.com/js-monthly/ Follow Lewis: Twitter: https://twitter.com/WuigPrescott Next: 👉 Check Previous video: Heavily Connected Data Applications - https://youtu.be/D7C-97HgXTs —————————————————— 📚 Learn more about Prisma • Website: https://www.prisma.io • Docs: https://www.prisma.io/docs • Quickstart: https://pris.ly/qstart —————————————————— ❓ Get help with Prisma issues • Slack: https://slack.prisma.io • GitHub: https://www.github.com/prisma/prisma/discussions • Stackoverflow: https://stackoverflow.com/questions/tagged/prisma —————————————————— 💬 Follow Prisma on social media • Twitter: https://twitter.com/prisma • Instagram: https://www.instagram.com/prisma.io/ • TikTok: https://www.tiktok.com/@prismadata • Facebook: https://www.facebook.com/prisma.io • LinkedIn: https://www.linkedin.com/company/prisma-io —————————————————— 🔠Professional captions for your technical videos Prisma sponsors human-reviewed, professional closed captions for ANY video valuable to our community (for example, about: Node.js, TypeScript & Type Safety, Prisma, databases, etc). Get your FREE captions here: https://pris.ly/closedcaptions —————————————————— ✅ Subscribe to Prisma's YouTube channel https://www.youtube.com/channel/UCptAHlN1gdwD89tFM3ENb6w?sub_confirmation=1

In this STET Session, Lewis Prescott has explained and practically demonstrated about the process of using JavaScript for API Testing. 𝐀𝐠𝐞𝐧𝐝𝐚: - Why JavaScript for API Testing? - Supertest framework for API Testing - Nock for mocking - Integration Tests with Supertest and Nock 𝐐&𝐀: - Why API Testing using JavaScript? - Preferable Use cases for API Testing? - API Testing or UI Functional Testing? - Different Frameworks available for API Testing? - Common Test Failures while performing API Testing? - Performing API Testing when the feature is under development? - Planning API Testing in a Project? - API Testing falls under White box or Black box? - Learning path for beginner in API Testing?

Testing is everyone’s responsibility. At Cancer Research UK we have overcome many barriers and challenges to making End to End tests a first class citizen inside the continuous integration pipeline. Some of which I will present in this talk: - Introducing the term "Acceptance Tests" instead of End to End Tests - Page Object Model vs App Actions - BDD vs Vanilla JS - Horizontal End to End Tests vs Vertical End to End Tests I hope our journey will align with many other people’s current, past or future experience, potentially encouraging some people to take the leap and make automated testing a team responsibility. A bit about Lewis: Currently a QA Lead at Cancer Research UK. Lewis specialises in API and Contract testing, and especially enjoys pair programming and training developers to be better testers. Lewis loves to share and teach others the craft of testing and has also volunteered at Code Club UK teaching programming basics to the next generation of QA’s.

Speaker – Lewis Prescott, QA Automation Lead at Cancer Research UK (https://www.linkedin.com/in/lewis-prescott-12409a44/) Summary: Serverless architecture has many benefits and testability is one of them. Using Moto and Pytest I will share my experience of unit testing in this environment. At Cancer Research UK we are working alongside AstraZeneca to build a solution which allows scientists to identify DNA patterns of cancerous cells using AWS lambdas. About the speaker: Lewis is currently the QA Automation Lead at Cancer Research UK. He enjoys conversations about testability, automation and contract testing. In his spare time, he likes to run, cycle and drink ale, this year he's meant to be running to Paris...

Contract Testing offers a tool which can help mitigate the risk of your releases in a micro-services infrastructure, equivalent to TDD but with API documentation. Pact is not just a framework but a tool to facilitate change within your organisation. Want to release with confidence? Want to find issues before integration environment? Want a better solution to end-to-end tests? About our Speaker, Meet Lewis "QA Automation Lead at Cancer Research UK. My expertise lies in testability of code, CI/CD and API testing. Tools that I’m excited about at the moment: Cypress, Pact, Axe, Github Actions. I love to share my knowledge with others young and old, from test automation techniques with experienced developers to basic python with primary school children at code club. Outside of work, this year I will be running to Paris as part of a relay with 4 friends and Swimming 3km in the arctic circle (Corona virus permitting)."