Tidbits tagged with #testing (21)

post topics:
Continue reading →

does not really exist in c
what to inject?
Continue reading →

Archijs describes itself as "A package to test javascript architecture".
TL;DR - it is not ready for use yet, I would not.
Continue reading →

I used [axios] in a project and while I was reading the docs to learn how multiple interceptors work, I had to dig all the way into the tests and into the source code to finally understand it fully.
Continue reading →

In part 1 I started my naive investigation on how to apply machine learning for making visual regression tests (VRT) better. I described the problem to solve, explored Keras very superficially and did also touched on the complexity of doing ML myself as opposed to having colleagues who are experts and who throw phrases like "train a model" and "predict" etc. around.
Oh boy, did I underestimate this.
Continue reading →

I broke this site, and thanks to @Holger reporting the error I figured out I should have done more testing instead of just tweeting that I should :).
Continue reading →

Learning stuff about nodejs (or v8) while writing tests that ensure runtime behaviour, using process.cpuUsage and process.memoryUsage. Curious how brittle those tests become over time. Glad the app ALWAYS runs in the same docker container (dev and prod).
Continue reading →

Why a #mocha #test times out, when I write it like this: it('...', _ => {}); but it does NOT time out, when I write: it('...', () => {});? Exactly, because the _ is the magic done, that one needs to call.
Continue reading →

While refactoring some badly tested code, a pattern of how I extract dependencies emerged. The actual intention was to improve the testability. In this case dependency injection is the tool that helped me. Read here to find out the steps I found to separate the dependencies.
Continue reading →

Welcome to the JS (and) Crafting #1 - February 28th, 2017. Every Monday you will receive a hand-selected collection of links about JavaScript and how to craft better software. Let's get started ...
Continue reading →

An undone blog post - More explicit assert with hamjest
Continue reading →

A very good talk by Jim Weirich, where he shows how to pull the meat, the actual business logic out of a rails app to make it testable in a fast manner concludes with a very interesting idea.
Continue reading →

Emily Bache in her talk "Catch Dancing Ponies — Try Approval Testing" makes me balance my attitude where I try to prevent intergration tests, finding the right amount is the thing to do, I guess. Using this TextTest seems to be one way.
Continue reading →

From The Clean Code Talks this is a very good one by Misko Hevery where he is talking us out of using IFs, or at least trying to explain what IFs actually mean in code. And how we can better cater for those cases using polymorphism and how this also enables us to test better.
Continue reading →

How to be a great software developer is a looong read, but it's worth reading, since it contains lots of truths.
Continue reading →

This is a great talk by @KevlinHenney
Continue reading →

I don't get mocha to build with browserify, I always get
Continue reading →

a talk by Chad Fowler
Continue reading →

Mocks Aren't Stubs
Continue reading →

Watch the author of poodr describing how to solve the problem of mocks and real code running out of sync! (And lots of goodies about testing and stuff.) Watch it twice, it's worth it :)
Continue reading →

IDEs are awesome, but sometimes in my way and setting up test runners sometimes defeats the purpose of being fast with tests, which also means having feedback constantly and continuously.
Continue reading →