Skip to content

Instantly share code, notes, and snippets.

@andywer
Last active December 23, 2020 17:22
Show Gist options
  • Save andywer/115b7e76b6fc8d3ce00ce19d0c6280a3 to your computer and use it in GitHub Desktop.
Save andywer/115b7e76b6fc8d3ce00ce19d0c6280a3 to your computer and use it in GitHub Desktop.

Revisions

  1. andywer revised this gist Aug 11, 2017. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion talk-proposal.md
    Original file line number Diff line number Diff line change
    @@ -12,7 +12,7 @@ Instead of manual debugging it provides a structured approach to fix or even pre

    ## Talk Content

    In this talk I would like to show you how to write a leakage test to fix a common leak scenario and make sure it is gone for good!
    I will show you how to write a leakage test to fix a common leak scenario and make sure it is gone for good!

    Leakage is a quite unique tool, since it not only helps you debug leaks, but actually allows writing leakage tests using Mocha, Jest, AVA, tape and friends. You can use it to prove that your code does not leak and write regression tests for leaks you fixed.

  2. andywer revised this gist Aug 10, 2017. 1 changed file with 7 additions and 3 deletions.
    10 changes: 7 additions & 3 deletions talk-proposal.md
    Original file line number Diff line number Diff line change
    @@ -4,13 +4,17 @@ This is a proposal for lightning talk at [Reactive Conf](https://reactiveconf.co

    Hi, I am [Andy](https://github.com/andywer), creator of [leakage](https://github.com/andywer/leakage) - the node-powered memory leak testing library.

    It is special compared to previous tools because it not only helps you debug leaks, but actually allows writing leakage tests using Mocha, Jest, AVA, tape and friends. You can use it to prove that your code does not leak and write regression tests for leaks you fixed.
    Instead of manual debugging it provides a structured approach to fix or even prevent memory leaks.

    Instead of manual debugging it provides a structured approach to handle or prevent memory leaks in the first place.
    <p align="center">
    <img src="https://media.giphy.com/media/xT5LMXBrV5NkVZHKms/giphy.gif?" />
    </p>

    ## Talk Content

    πŸ‘‰ In this talk I would like to show you how to write a leakage test to fix a common leak scenario and make sure it is gone for good!
    In this talk I would like to show you how to write a leakage test to fix a common leak scenario and make sure it is gone for good!

    Leakage is a quite unique tool, since it not only helps you debug leaks, but actually allows writing leakage tests using Mocha, Jest, AVA, tape and friends. You can use it to prove that your code does not leak and write regression tests for leaks you fixed.

    Despite writing OSS for several years, I have never given a talk at a conference. So I am particularly looking forward to this!
    If you like the idea, please 🌟 the gist and spread the word 😊
  3. andywer revised this gist Jun 23, 2017. 1 changed file with 0 additions and 3 deletions.
    3 changes: 0 additions & 3 deletions talk-proposal.md
    Original file line number Diff line number Diff line change
    @@ -16,6 +16,3 @@ Despite writing OSS for several years, I have never given a talk at a conference
    If you like the idea, please 🌟 the gist and spread the word 😊

    Cheers!


    <p align="center"><img src="https://github.com/andywer/leakage/raw/master/docs/failing-test.png?raw=true" /></p>
  4. andywer revised this gist Jun 23, 2017. 1 changed file with 3 additions and 0 deletions.
    3 changes: 3 additions & 0 deletions talk-proposal.md
    Original file line number Diff line number Diff line change
    @@ -16,3 +16,6 @@ Despite writing OSS for several years, I have never given a talk at a conference
    If you like the idea, please 🌟 the gist and spread the word 😊

    Cheers!


    <p align="center"><img src="https://github.com/andywer/leakage/raw/master/docs/failing-test.png?raw=true" /></p>
  5. Andy Wermke revised this gist Jun 23, 2017. 1 changed file with 0 additions and 0 deletions.
    Binary file removed leakage.gif
    Binary file not shown.
  6. Andy Wermke revised this gist Jun 23, 2017. 1 changed file with 0 additions and 0 deletions.
    Binary file added leakage.gif
    Loading
    Sorry, something went wrong. Reload?
    Sorry, we cannot display this file.
    Sorry, this file is invalid so it cannot be displayed.
  7. andywer revised this gist May 26, 2017. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions talk-proposal.md
    Original file line number Diff line number Diff line change
    @@ -14,3 +14,5 @@ Instead of manual debugging it provides a structured approach to handle or preve

    Despite writing OSS for several years, I have never given a talk at a conference. So I am particularly looking forward to this!
    If you like the idea, please 🌟 the gist and spread the word 😊

    Cheers!
  8. andywer revised this gist May 26, 2017. 1 changed file with 4 additions and 5 deletions.
    9 changes: 4 additions & 5 deletions talk-proposal.md
    Original file line number Diff line number Diff line change
    @@ -4,14 +4,13 @@ This is a proposal for lightning talk at [Reactive Conf](https://reactiveconf.co

    Hi, I am [Andy](https://github.com/andywer), creator of [leakage](https://github.com/andywer/leakage) - the node-powered memory leak testing library.

    It is special compared to previous tools, because it not only helps you debug leaks, but actually allows writing leakage tests using Mocha, Jest, AVA, tape, ...
    You can use it to prove that your code does not leak and write regression tests for leaks you fixed.
    It is special compared to previous tools because it not only helps you debug leaks, but actually allows writing leakage tests using Mocha, Jest, AVA, tape and friends. You can use it to prove that your code does not leak and write regression tests for leaks you fixed.

    Instead of manual debugging it provides a structured approach to handle or even prevent memory leaks in the first place.
    Instead of manual debugging it provides a structured approach to handle or prevent memory leaks in the first place.

    ## Talk Content

    πŸ‘‰ In this talk I would like to show you how to write a leakage test to fix a common leak scenario and make sure it is gone for good!

    Despite writing OSS for several years, I have never given a talk at a conference. So I am particularly looking forward to this! 😊
    If you like the idea, please 🌟 the gist and spread the word πŸ˜‰
    Despite writing OSS for several years, I have never given a talk at a conference. So I am particularly looking forward to this!
    If you like the idea, please 🌟 the gist and spread the word 😊
  9. andywer revised this gist May 26, 2017. 1 changed file with 5 additions and 5 deletions.
    10 changes: 5 additions & 5 deletions talk-proposal.md
    Original file line number Diff line number Diff line change
    @@ -2,16 +2,16 @@ This is a proposal for lightning talk at [Reactive Conf](https://reactiveconf.co

    # Memory Leak Testing in 2017

    Hi, I am [Andy](https://github.com/andywer), creator of [leakage](https://github.com/andywer/leakage) - a JavaScript memory leak testing library.
    Hi, I am [Andy](https://github.com/andywer), creator of [leakage](https://github.com/andywer/leakage) - the node-powered memory leak testing library.

    It is special compared to previous tools, because it does not only help you debugging leaks, but actually allows writing leakage tests using Mocha, Jest, AVA, tape, ...
    You can use it to prove that your code does not leak and write regression tests.
    It is special compared to previous tools, because it not only helps you debug leaks, but actually allows writing leakage tests using Mocha, Jest, AVA, tape, ...
    You can use it to prove that your code does not leak and write regression tests for leaks you fixed.

    Instead of manual debugging it provides a structured approach to handle or even prevent memory leaks.
    Instead of manual debugging it provides a structured approach to handle or even prevent memory leaks in the first place.

    ## Talk Content

    πŸ‘‰ In the talk I would like to show you how to write a leakage test to fix a common leak scenario!
    πŸ‘‰ In this talk I would like to show you how to write a leakage test to fix a common leak scenario and make sure it is gone for good!

    Despite writing OSS for several years, I have never given a talk at a conference. So I am particularly looking forward to this! 😊
    If you like the idea, please 🌟 the gist and spread the word πŸ˜‰
  10. andywer created this gist May 26, 2017.
    17 changes: 17 additions & 0 deletions talk-proposal.md
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,17 @@
    This is a proposal for lightning talk at [Reactive Conf](https://reactiveconf.com/). **Please 🌟 this gist to push the proposal!**

    # Memory Leak Testing in 2017

    Hi, I am [Andy](https://github.com/andywer), creator of [leakage](https://github.com/andywer/leakage) - a JavaScript memory leak testing library.

    It is special compared to previous tools, because it does not only help you debugging leaks, but actually allows writing leakage tests using Mocha, Jest, AVA, tape, ...
    You can use it to prove that your code does not leak and write regression tests.

    Instead of manual debugging it provides a structured approach to handle or even prevent memory leaks.

    ## Talk Content

    πŸ‘‰ In the talk I would like to show you how to write a leakage test to fix a common leak scenario!

    Despite writing OSS for several years, I have never given a talk at a conference. So I am particularly looking forward to this! 😊
    If you like the idea, please 🌟 the gist and spread the word πŸ˜‰