You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current benchmark/README.md is in fact a guide on how to run and write benchmarks, I suggest we move this to doc/guides (where writing-tests.md is) and create another README.md that explains the directory layout/common API (like what test/README.md does).
I think it makes sense to have a README that explains how to run the benchmarks in the benchmarks directory, but I do think that the guide on how to write one should be in guides (linked from the readme)
Reacted by Claudio Rodriguez, Gibson Fahnestock and Adrián Estrada
I think it makes sense to have a README that explains how to run the benchmarks in the benchmarks directory, but I do think that the guide on how to write one should be in guides (linked from the readme)
I agree, the same can be done to test/README.md too. I'll prepare a PR for that :)
Activity
evanlucas commentedon Feb 6, 2017
I think it makes sense to have a README that explains how to run the benchmarks in the benchmarks directory, but I do think that the guide on how to write one should be in guides (linked from the readme)
joyeecheung commentedon Feb 7, 2017
I agree, the same can be done to test/README.md too. I'll prepare a PR for that :)
doc: add benchmark/README.md and fix guide
doc: improve test/README.md
doc: move benchmark/README.md to doc/guides
doc: add benchmark/README.md and fix guide
doc: improve test/README.md
doc: improve test/README.md
doc: improve test/README.md
doc: move benchmark/README.md to doc/guides