Coding Jag Edition 100 and more to come!
Welcome to the 100th edition of Coding Jag brought to you by LambdaTest!
100!? Yes, we’ve been ‘Ja(o)gging’ for 100 editions now!???
When we started with Coding Jag, all we had was a vague idea. We wanted to curate the best content from across the testing community for our readers. The reason was simple— the QA and developer world of today is fast changing and people are finding it hard to stay abreast with it.???
Cut to today, we have almost 100k subscribers with a sizeable chunk of them diligently reading it week after week. We are truly humbled by your love!???
We want to thank our readers and the overall QA and developer community for constantly inspiring us with your ideas, blogs, videos, tutorials, podcasts, and whatnot! We wouldn’t exist without you!
Going forward, you can expect us to experiment a bit but we’ll constantly stay true to the reason why we began in the first place.?
With that, et voila, our 100th episode! ????
Cheers,
Team LambdaTest
News?
Knowledge is power, but the knowledge that is shared is much more effective. Dive into how testing on shared knowledge might push testers to become better.
This article outlines the approach to testing server-less applications and how it helps promote productivity and prompt client problem-solving.
In the world of tech, learn how knowing when to coach, when to train and when to mentor a product team helps achieve quality.?
Deep-dive into an interesting experiment that the author did with Gherkin.?
Why do you enjoy testing and how does it reflect in a tester's work? This blog seeks the answers to what makes testing fun.
Performance
In this step-by-step guide, you can learn how JMeter easily integrates with Selenium which can be used for conducting performance testing.
Here is an introduction to the Fedora Silverblue, and why Immutable OS is the future.?
Automation
In this tutorial, learn how you can handle errors and exceptions in Selenium Python while performing automation testing.?
In this 3 post series, learn and master the use case of Factory Pattern to construct various browser instances for either local or remote execution with Selenium WebDriver.
This blog highlights and shares the real-life experience of the best Design Patterns for QAs to use during test solutions creation.
Test automation is automation of a test/check against any interface. Not necessarily a GUI. Test automation is a whole wide spectrum that includes unit, integration and end-end tests along with UI. It is time to get past the herd behavior and get UI test automation off the pedestal.
Tools
Take a look at this year's top UI automated testing tools while learning about the challenges associated while running UI tests and how to solve them.
Here is a list of the several different open-source automation tools for testing Windows desktop apps that have been rated using the essential standard criteria.
Others
In this Playwright tutorial, gets started with the Page Object Model (POM) and how to use TypeScript to create and run POM tests in Playwright.
This webinar explains where bugs come from and how to make sure they don’t return, to how to not break working features as you fix the bugs.?
In this week's episode, the peers discuss the safety net around levels of testing and how it may enable the business to take more risks.?
Thanks for reading! Like what you see? ?? Hit "Subscribe" and?Follow?us on?LinkedIn?and never miss another update. Feel free to check out our?previous editions!
?? Software Engineer - I @ Calrom | Full Stack Dev | .NET Core | React.js | Web Dev | Gold MLSA & MCT @ Microsoft ????
2 年Thankyou for featuring my article - ???
Lead Software Engineer @ Carousell | Software Quality | Co-organizer of taqelah
2 年Hey LambdaTest. Thanks for featuring my article "A pied piper named UI test automation". Appreciate :) Just for the record, the highlight of my article is exactly opposite of "Explore what led to the global adoption of UI Test Automation and why?it is still on a pedestal." Instead the point I'm trying to make with that article is why we *should NOT* be keeping UI test automation on the pedestal, and treat test automation as a context driven activity where automated tests could be anything from unit, component, integration to end-end tests with or without the UI.