You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While running acceptance tests, I found that one test is failing because the error message we expect (and validate) is different than the error message we are receiving.
While running TestRepo/repo-set-default, we do:
# Ensure that no default is set
cd $SCRIPT_NAME-$RANDOM_STRING
exec gh repo set-default --view
stderr 'no default repository has been set; use `gh repo set-default` to select one'
But the output while running the test is:
# Ensure that no default is set (2.091s)
> cd $SCRIPT_NAME-$RANDOM_STRING
$WORK/repo_set_default-oaJIlaRWss
> exec gh repo set-default --view
[stderr]
X No default remote repository has been set. To learn more about the default repository, run: gh repo set-default --help
> stderr 'no default repository has been set; use `gh repo set-default` to select one'
FAIL: testdata/repo/repo-set-default.txtar:10: no match for "no default repository has been set; use `gh repo set-default` to select one" found in stderr
If I change the test to do:
# Ensure that no default is set
cd $SCRIPT_NAME-$RANDOM_STRING
exec gh repo set-default --view
stderr 'No default remote repository has been set. To learn more about the default repository, run: gh repo set-default --help'
While running acceptance tests, I found that one test is failing because the error message we expect (and validate) is different than the error message we are receiving.
While running
TestRepo/repo-set-default, we do:But the output while running the test is:
If I change the test to do:
then the test passes.