Skip to content

Latest commit

 

History

History
31 lines (27 loc) · 2.24 KB

README.md

File metadata and controls

31 lines (27 loc) · 2.24 KB

Bestest - benchmarking tooling

CircleCI Maintainability Test Coverage lerna

Work in progress...

To do list

  • Task scheduling: to set-up different methods for scheduling tasks (on different environments)
  • Time measurement: to set-up different methods to estimate current time (on different environments)
  • Function performance measurement: to run simple benchmarks against function, getting information about execution time or ops/sec
  • Detect environment information: to gather information for current environment
  • File system: to allow in-memory computations in compiler
  • Compiler: to prepare code for use
  • Statistics & formatting utils: to consume function performance information
  • Node.js execution sandbox: to run test code in memory sand-boxed environment, with possibility to mock file system
  • Runner: run code on different environments automatically
  • Output tools: output benchmark results in many different ways (HTML, SVG, console)
  • Core: core tooling: test suites and cases, and their factories
  • Bestest itself: to combine all utils
  • CLI: Simple CLI interface for Bestest tool
  • Unit tests: with Mocha and Wallaby
  • Examples
  • Documentation
  • Different compilers: already existing: Webpack, transparent one
  • Different output tools: none yet
  • Different environment runners: already existing: local
  • Check on Windows machines