The Only Two Tests That Matter

Most tests are meaningless noise. If you want to do it right, only two types matter:

Component Tests – Test behavior, not mocks. Fake external services, ensure input/output works, and confidently. With that it’s easy to generate API docs & client libs without experience pact tests.

E2E Tests – Run 24/7, track real user behavior, log metrics, measure uptime, bugs, performance, and resilience. No need for e2e tests in CI pipelines if testing every environment.

Both test behavior, not code. You can refactor without touching tests as they only break when behavior breaks. If tests are slow, your implementation is the problem. Even a Raspberry Pi can handle it.

And above all: Tests must run locally. No excuses. It’s important for debugging and reproduction of user behaviors.

I just released `playwright-opentelemetry-reporter`, a custom reporter for Playwright that generates @opentelemetry spans from test cases and steps! If you want to bring some observability to your Playwright, try it out! https://github.com/aergonaut/playwright-opentelemetry-reporter

If you're looking for an example in the wild of testing copy/paste functionality in an end to end test using Playwright, I gotchu in this latest pull request for the OpenSauced app. #opensource #e2etesting #testing

https://github.com/open-sauced/app/pull/3538

> Let’s have a look at an example that could be affected by 3rd party code and ways to monitor your stack with Playwright to guarantee that no external providers or ad blockers can mess with your business.

https://www.checklyhq.com/blog/how-playwright-can-monitor-third-party-resources/

I am currently searching for an #E2ETesting library. The most important thing for me to test, which I probably cannot test in a different way, is native browser notifications after receiving a push notification from a #JavaScript #ServiceWorker.

Solutions I know of include #Selenium, #WebDriverIO, #Playwright, #NightWatch and #Cypress.

Do you have any other ideas or opinions on those testing libraries?

Going to add a few thoughts for some of them in separate toots.

Manchmal sitze ich einfach da, gebe `npx playwright test` ein und entspanne. #e2etesting #playwright

I'm building an app with as little #JavaScript as possible (only sending and receiving push notifications). I don't use any framework, and everything else is handled by the server.

Now I'm wondering how to handle #testing. Does it make sense to do #UnitTesting for a few lines of JavaScript? How do you handle that? Do you only do #E2ETesting in such cases?

I was already thinking about using #JSDom in #Jest, but the #HTML is generated by #Symfony, making it hard to get it in there…

The video from my talk Exploring better ways to write tests is now available: https://www.youtube.com/watch?v=dZX7SbGOGn4

I gave it at this year's Nordic Testing Days 2023 in Tallinn, and I discussed my journey from feeling dissatisfied with testing tools to creating my own test runner. My goal of this talk was to inspire others to explore and customize their tools rather than settling for the default options available.

Slides and more at https://coderbyheart.com/exploring-better-ways-to-write-tests

I think that "write a test for every bug" is a foolish advice.

Write #tests for business logic only. Everything else is an implementation detail.

Now that #AI can write #code I think the smart career move is to get into #softwareTesting; defining success in a problem space was always the hard part of #softwareDevelopment and will need even better tools now!

#Programming code was never the point of #software.

Do you run into end-to-end tests against a staging environment?

Check out our video on testing. We talk about getting the most out of your tests and avoiding the pitfalls that drag on many teams and distract teams from the goal of building quality software.

#Flutter and #iOS devs in particular will find this interesting. We talk about full app widget testing

#flutterdev #unittesting #integrationtesting #e2etesting

https://youtu.be/3dKugGP0LAc

Going neck deep in some more end-to-end testing today. #e2eTesting

I figure if we build this thing one brick at a time, at the end of a year, I'll have a little brick QA shack by the end of it.

Automated web app testing startup ProdPerfect raises $13M Series A led by Anthos Capital - This morning ProdPerfect, a technology startup focused on web application testing, announced a $13 m... more: http://feedproxy.google.com/~r/Techcrunch/~3/oGpyr-V7G6Y/ #thewebisabigplace #fundings&exits #anthoscapital #prodperfect #e2etesting #startups #testing #tc