hhvm / hacktest

A unit testing framework for Hack

hhvm/hacktest Issues

[ RFC ] Add a typesafe infrastructure for DataProvider tests which use generics.
Closed a year ago3
Skipping test in `beforeTestAsync` /sometimes/ leads to a non-zero exit
Updated a year ago
CLI: if no paths given and tests/ exist, print a warning to STDERR but run with tests/
Closed 2 years ago
[ Lint ] Pull in the changes to the tests in hhvm/hsl to pass the DataProviderTypesLinter
Closed 2 years ago
Skipped tests should show skip reason, at least in verbose mode
Updated 4 years ago
Error if dataprovider keys include periods
Updated 5 years ago1
Refactor for testability and clearer error reporting
Closed 5 years ago
add <<TestGroup('foo')>> feature or similar (like `@groups` in PHPUnit) to run a specific subset of tests
Closed 5 years ago2
Verbose output does not include actual error frame - trace starts one frame out
Closed 5 years ago2
Assertions
Closed 5 years ago2
Support .hack test files
Closed 5 years ago1
Add progress indication when things are running
Updated 5 years ago
Migrate PhpUnit to Hacktest methods that start with `should` instead of `test`.
Closed 5 years ago3
Wrap [.EF] CLI output at terminal width
Updated 6 years ago
CLI output starts with a blank line
Closed 6 years ago
CLI output is truncated
Closed 6 years ago
Provide more detailed output
Closed 6 years ago1
Non-verbose output should search for filename, not class name
Closed 6 years ago
Provide location of assertion in backtrace
Closed 6 years ago1
"Only test methods and data providers can be public" message for a dataprovider
Updated 6 years ago2
Add command to .travis.sh to run tests for/with the new runner
Closed 6 years ago1
Add documentation to the readme
Closed 6 years ago3
Parallization (DontAwaitInALoopLinter)
Updated 6 years ago2
Add test to make sure that concrete test classes can be grandchild classes
Updated 6 years ago
Add tests to check that the CLI returns the correct exit code
Closed 6 years ago
Refactor handling of dataproviders to reduce duplication
Closed 6 years ago
Handle (and test) dataProviders that return no rows, or throw errors (including marking the test as skipped)
Closed 6 years ago
Make a distinction between failures and errors
Closed 6 years ago
Include additional information in test result
Updated 6 years ago
Use structured data for progress
Closed 6 years ago1
Indicate failure with exit code
Closed 6 years ago
Make HackTestCase strict
Closed 6 years ago
Why is call_user_func_array used?
Closed 6 years ago1