-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fishtape 2 #31
Comments
Sound nice. I will recommend to use the command substitution syntax |
@edouard-lopez To isolate your test you have two options.
begin
pushd /path/to/some/dirty/git/repo
git_is_dirty
test "git_is_dirty shows changes not staged for commit" $status = 1
popd
end
test "git_is_dirty shows changes not staged for commit" (
pushd /path/to/some/dirty/git/repo
git_is_dirty
echo $status
popd
) = 1 |
Instead of overloading the This helps make clear when you are writing a test or using the if test "$version" = 3.0.0
@test "Has some file" -f somefile
end |
BATS, the test framework for bash use |
🎉 I'm done implementing everything. See the changelog: |
Fishtape 2 will break the test syntax as we want to make it compatible with
fish_indent
#32, #34.Summary
fish_indent
--pipe
in favor of any userland solution like"fish -c "fishtape *.fish | tap-nyan"
test
array extensions (don't know what I am talking about? don't worry then)Here's the new test syntax I have in mind. See that
test
blocks are now gone. Thetest
builtin has been "enhanced" to take an optional test description. If you already know how to use the shell'stest
builtin you already know how to create valid assertions in Fishtape 2.Notice that there is no reason you couldn't write the last test from above as follows (if you prefer):
Issue History
@test
instead oftest
Fishtape 2 #31 (comment)The text was updated successfully, but these errors were encountered: