Incremental Tests

Before we wrap up our build optimization work, there’s one more optimization to make: incremental testing. Our server code and client code are completely independent, which means we don’t need to test one if the other has changed. With a bit of work, we include that rule in our build. When we’re done, our best-case build only takes a fraction of a second.

  1. LL16JavaScript Workflow 2015

    Fri, 6 Feb ’15
  2. E278Slack === Speed

    Wed, 4 Feb ’15
  3. E279Quick Build

    Mon, 9 Feb ’15
  4. E280Fast Tests

    Wed, 11 Feb ’15
  5. E281Incremental Builds

    Mon, 16 Feb ’15
  6. E282Lint Rules!

    Wed, 18 Feb ’15
  7. E283A Real Programming Language

    Mon, 23 Feb ’15
  8. E284Performance Optimization and Profiling

    Wed, 25 Feb ’15
  9. E285Up In Flame Graphs

    Mon, 2 Mar ’15
  10. E286From Synchronous to Asynchronous

    Wed, 4 Mar ’15
  11. E287From Asynchronous to Synchronous

    Mon, 9 Mar ’15
  12. E288Integrating Our Spike

    Wed, 11 Mar ’15
  13. E289Incremental Tests

    Mon, 16 Mar ’15
  14. E2900.14 seconds

    Wed, 18 Mar ’15