Learnings

<p>Improving React Testing Library Tests </p>

<p>Organizing tests with jest projects </p>

<p>TIL: if you need to use both override_flag (django-waffle) and either django_assert_num_queries (pytest-django) or assertNumQueries (django testcase), make sure to have override_flags being put first or you'll end up tainting your number of queries assertion with those from flag value override</p>

<p>Why Is My Jest Test Suite So Slow </p>

<p><em>Expanding our Front End Testing Frameworks</em> </p>

<p>Investing in Unit Testing </p>

<p>Testing Mutation and Actions in Vuex </p>

<p>How to test a value in Brazilian Reais converted by the JavaScript internationalization API </p>

<p>Cypress Component Testing Beta </p>

<p>Patterns of flakey Python tests: </p>

<p>How to test the callbacks passed to Django's transaction.on_commit</p>

<p>assertLogs - A context manager to test that at least one message is logged on the logger or one of its children, with at least the given level </p>

<p>A collection of public resources about how software companies test their software: </p>

<p>Why We Killed Our End-to-End Test Suite: </p>

<p>django-capture-on-commit-callbacks: Capture and make assertions on () callbacks. This allows you to write your tests with the TestCase, rather than needing the slower TransactionTestCase to actually commit the transactions: </p>

<p>django-recaptcha now requires mocking for unit testing: </p>

<p>To avoid flooding your terminal with a long list of failed tests, stop at the first failure on pytest using the -x flag </p>

<p>Bash script to get the HTTP status code of a list of urls: </p>

<p>Don't put logic in tests: </p>

<p>How to actually test UIs </p>

<p>If you're using pytest-xdist, you can define a watcher using the flag <code>-f</code> so that every time you update a file it runs the test suite initially defined.</p>

<p>Effective testing for machine learning systems: </p>

<p>Why do you need performance tests? </p>

<p>Common mistakes with React Testing Library </p>