Add test harness using ts

[thinkerbot]

ts is a shell testing library that might serve the needs of shellfire, at least for testing leaf functions. This adds a couple examples and a basic test harness.

Notes

• I wrote ts and naturally I like it but no worries if this is not your style. Seriously I will not be offended.
• This covers pretty much all that ts provides. You get a function to assert_status and another one to assert_output, you get a $ts_test_dir variable that you can make into a dir and to store test-specific files, you get a setup and a teardown function. Not much else. Each test is run in a subshell to prevent carryover. You have to orchestrate the rest to your liking.
• To get ts, clone the repo and add the bin dir to PATH. You might just want to vendor it, it's just one file.

[stormmq]

Simon

Looks interesting. Im travelling now until Thu - will get back in touch
then.
On 20 Jan 2015 16:12, "Simon Chiang" [email protected] wrote:

ts https://github.com/thinkerbot/ts is a shell testing library that
might serve the needs of shellfire, at least for testing leaf functions.
This adds a couple examples and a basic test harness.
Notes

I wrote ts and naturally I like it but no worries if this is not your
style. Seriously I will not be offended.

This covers pretty much all that ts provides. You get a function to
assert_status and another one to assert_output, you get a $ts_test_dir
variable that you can make into a dir and to store test-specific files, you
get a setup and a teardown function. Not much else. Each test is run
in a subshell to prevent carryover. You have to orchestrate the rest to
your liking.

To get ts, clone the repo and add the bin dir to PATH. You might just
want to vendor it, it's just one file.

---

You can view, comment on, or merge this pull request online at:

#3
Commit Summary

• Add test harness using ts

File Changes

• A .gitignore
  https://github.com/shellfire-dev/core/pull/3/files#diff-0 (2)
• A test/helper
  https://github.com/shellfire-dev/core/pull/3/files#diff-1 (6)
• A test/suite
  https://github.com/shellfire-dev/core/pull/3/files#diff-2 (19)
• A variable/variable.test.functions
  https://github.com/shellfire-dev/core/pull/3/files#diff-3 (63)

Patch Links:

• https://github.com/shellfire-dev/core/pull/3.patch
• https://github.com/shellfire-dev/core/pull/3.diff

—
Reply to this email directly or view it on GitHub
#3.

[raphaelcohn]

We use #!/usr/bin/env sh for shellfire scripts so that we don't force a particular shell on folks.

[raphaelcohn]

It's a good little set of ideas. I think this fits best in shellfire as another module (like core, like build) with a set of functions and a ready-to-use driver (see the build program in the 'build' module). We then link it into the shellfire-dev/shellfire README.

Additionally, we might be able to use introspection ('reflection') using declare -F (we'll have to check dash) to find all functions starting, say, _test_NAMESPACE, and just run the lot (_test because 'test' would be the test namespace for things like assert, ie test_assertOutput or, if there's test/assert, test_assert_output).