bucharest-gold / perf-quest Goto Github PK

Add simple test case for this.

The current steps are:

1. Enter on directory 'x vs y'
2. make
3. Doing nothing with bench result.
4. node --prof prof-x.js
5. node --prof-process isolate-.log
6. copy summary to prof-x.js
7. rm isolate-.log
8. node --prof prof-y.js
9. node --prof-process isolate-.log
10. copy summary to prof-y.js
11. rm isolate-.log

Is good to have a second affirmation.

• Try to identify blocs/techniques to create a comparison.

To link this with item 1. of bucharest-gold/entente#9 (comment)

Maybe is good to keep the focus on bench tools only.
This will make the process more simple to add new test cases.

Create a generic package.json and a eslintrc.json file to be copied to test case directory when run make.

This module is showing some instability.
Maybe is good to run only one time and compare the results with benchmark module.

Automation to 'join' txt files on README.md

The goal is to see the difference of extra hidden class creation.

http://lanceball.com/words/2016/10/14/data-hiding-in-es6/