v0.17.2

Fixes

• Adds a prepublishOnly script to correctly build package before publishing #68 - @lkipke

v0.17.1

Fixes

• Add lib/ and types/ to list of published files (#67) - @lkipke

v0.17.0

Features

• Rename default branch from master to main (#59) - @sjbarag
• Convert JS files to TS (#61) - @lkipke
• Add more diagnostics to tap reporting (#66) - @lkipke

Fixes

• Fix type comparison in assert#deepEquals (#64) - @vbuchii

v0.16.0

Features

• Searches the test/ and tests/ directories for component XML files, which will enable components that only exist in test cases.

v0.15.1

Fixes

• adds src/ to the files in package.json so that roca doesn't break when you try to run it

v0.15.0

Features

• Implemented code coverage reporting! Use the --coverage-reporters to generate coverage reports for your Brightscript code! (#56)

Chores

• Moved the assert API specs into the API section of the README for better discoverability (#54)

@hulu/roca 0.14.0

Features

• roca now supports parameterized tests via m.it_each (#50 / #47). See README.md for more details. Thanks @Vasya-M!

Bug Fixes

• The top-level roca BrightScript function now always returns an associative array (#52), even when tests fail. Nice catch, @lkipke!
• The -f commandline flag introduced in v0.11.0 wasn't available via its long-name --forbid-focused; now it is! Thanks @lkipke!

v0.13.0

• Adds test cases to the roca codebase 🎉 Thanks, @sjbarag!
• Fixes the behavior of nested beforeEach/afterEach to align with other testing framework standards
• Adds Github actions to automatically publish when a new release is created.

@hulu/roca 0.12.0

Features

roca learned the m.beforeEach and m.afterEach hooks that many other unit testing frameworks support (#20 / #42)! These allow for significantly reduced boiler-plate between tests. See README.md for more details.

@hulu/roca 0.11.0

Features

1. Variables added to the roca context with m.addContext() are now available on m inside of suites (#40)
2. A new CLI flag --forbid-focused causes roca to exit with a non-zero status code if fdescribe or fit are found in any test suite. It's handy for CI configurations where you don't want to accidentally disable most of your hard-earned tests! (#44)
3. Tests with the .test.brs extension can now be located in source/, components/, test/, or tests/, or any of their subdirectories! (#10 / #18 / #19)