*if you include word2vec.

https://jaketae.github.io/study/word2vec/#testing-the-model

In this video, we dive into Playwright's "page.goto()" and understand why it could be slowing down your end-to-end tests. We start with an example script and then walk you through the Playwright UI mode to understand how resource loading can delay the "page.goto()" call.

We also look into the different "waitUntil" configurations and check how they affect the speed of your tests. Enjoy, and drop any questions or comments below!

Blog post: https://www.checklyhq.com/blog/
"page.goto()" docs: https://playwright.dev/docs/api/class-page#page-goto
"addLocatorHandler" explained: https://www.youtube.com/watch?v=E8JLQoCDUcU

Learn why Microsoft's Playwright framework is a stellar solution for end-to-end testing and monitoring.

#playwright

Stefan Judis

With my open source work, I’ve historically taken an approach which relies more on integration... Tagged with perl, tdd, test2suite.

Test2::V0 provides a good base to work with, so we add that to our project’s requirements list straight away.

We’ll round that out with:

Test2::Require::AuthorTesting to skip certain tests when run on the end user’s machine, and require the AUTHOR_TESTING environment variable to run. This is useful for tests which are very slow or require a highly specific environment to run in.
Test2::Require::Module to skip certain tests when optional modules are unavailable.
Test2::Tools::Spec to better structure our unit tests.
Test2::Plugin::BailOnFail for when your tests simply cannot carry on. Use sparingly.

It's Hack Week again at SUSE. 🥳 An annual tradition where we all work on passion projects for a whole... Tagged with mojolicious, perl, javascript, node.

Avoiding a test count seems to be the trend in Perl modules these days. After all, automated test libraries in other languages don’t have anything similar, and they seem to get by fine. If the test fails in the middle, that can be detected by a non-zero exit code. It’s always felt like annoying bookkeeping, so why bother?

For simple tests like the above, I think that’s fine. Failing with a non-zero exit code has worked reliably for me in the past.

However, there’s one place where I think TAP had the right idea way back in 1988: event driven or otherwise asynchronous code. Systems like this have been popping up in Perl over the years, but naturally, it’s Node.js that has built an entire ecosystem around the concept. Here’s one of my tests that uses a callback system: