Learnings

<p>Node/Jest has a memory leak </p>

<p>Your Jest tests might be wrong </p>

<p>How writing tests can make you a faster and more productive developer </p>

<p>On the Diverse And Fantastical Shapes of Testing </p>

<p>Book Speed Up Your Django Tests: </p>

<p>Render HTML from a string to browser straight from Python (useful for debugging broken template/view tests!) </p>

<p>Tesla's Data Engine and what we should all learn from it: </p>

<p>What happens when you run manage.py test? </p>

<p>If you mock, are you even testing? </p>

<p>A collection of publicly available resources on how software companies in the world test their software systems and build their quality culture: </p>

<p>Mutpy: mutation testing tool for Python 3.3+: </p>

<p>Vaurien, the Chaos TCP Proxy </p>

<p>Comprehensive and exhaustive JavaScript &amp; Node.js testing best practices (August 2019) </p>

<p>Write tests. Not too many. Mostly integration. </p>

<p>Django Mock Queries, a library for mocking Django queryset functions in memory for testing: </p>

<p>Why You Only Need to Test with 5 Users</p>

<p><code>pytest-xdist</code> allows you to run failing tests in a loop inside a subprocess until it passes by looking for file changes to re-run previously failing tests. You can take advantage of it by having <code>pytest-xdist</code> installed and passing the command line flag <code>-f</code> or <code>--looponfail</code> to your pytest command. For more info see: #xdist-pytest-distributed-testing-plugin</p>

<p>Careful with negative assertions: </p>

<p>Unit testing anti-patterns: Structural Inspection </p>

<p>Subtests are the Best </p>

<p>Jest (JavaScript testing library) cheatsheet </p>

<p>polly.js: Record, replay, and stub HTTP interactions. </p>

<p>django-perf-rec is like Django's <code>assertNumQueries</code> on steroids! </p>

<p>Possible things that might go wrong when you're working with mock </p>