miller/go/regtest
John Kerl 367def54d7
Accept passing C->Go regtest cases within mixed-status suites (#543)
* Accept passing C->Go regtest cases within mixed-status suites

* Iterating on Windows regtest failures
2021-05-30 23:17:52 -04:00
..
cases Accept passing C->Go regtest cases within mixed-status suites (#543) 2021-05-30 23:17:52 -04:00
cases-non-windows Fix Windows regtest for --prepipe 2021-05-23 23:00:27 -04:00
cases-pending-go-port Accept passing C->Go regtest cases within mixed-status suites (#543) 2021-05-30 23:17:52 -04:00
cases-pending-windows Accept passing C->Go regtest cases within mixed-status suites (#543) 2021-05-30 23:17:52 -04:00
expected Make reg-test files relocatable (#493) 2021-04-13 16:23:10 -04:00
input Fix popen/EOF issue 2021-05-23 22:24:13 -04:00
README.md Make regression tests invokable from 'go test' (#491) 2021-04-12 23:00:53 -04:00

Miller regression tests

There are a few files unit-tested with Go's testing package -- a few dozen cases total.

The vast majority of Miller tests, though -- thousands of cases -- are tested by running scripted invocations of mlr with various flags and inputs, comparing against expected output, and checking the exit code back to the shell.

How to run the regression tests, in brief

Note: while this README.md file is within the go/regtest/ subdirectory, all paths in this file are written from the perspective of the user being cd'ed into the go/ directory, i.e. this directory's parent directory.

  • mlr regtest --help

  • go test -- TODO -- also comment

Items for the duration of the Go port

  • mlr regtest -c ... runs the C version of Miller from the local checkout

More details

TODO: needs to be written up

Creating new cases

TODO: needs to be written up