aboutsummaryrefslogtreecommitdiffhomepage
path: root/tests/interactive.fish
Commit message (Collapse)AuthorAge
* retry flakey tests on failureGravatar Kurtis Rader2016-04-11
| | | | Fixes #2926
* make testing on local servers hermeticGravatar Kurtis Rader2016-02-25
| | | | | | | | | | | | | | | | | | I noticed while fixing issue #2702 that the fish program being tested was sourcing config.fish files outside of the current build. This also happens when Travis CI runs the tests but isn't an issue there because of how Travis is configured to execute the tests. I also noticed that running `make test` was polluting my personal fish history; which will become a bigger problem if and when the fishd universal var file is moved from $XDG_CONFIG_HOME to $XDG_DATA_HOME. This change makes it possible for an individual to run the tests on their local machine secure in the knowledge that only the config.fish and related files from their git repository will be used and doing so won't pollute their personal fish history. Resolves #469
* fix unit tests related to the escape timeoutGravatar Kurtis Rader2015-12-23
|
* tests/bind.expect: re-enable but at human typing speed onlyGravatar David Adam2015-10-18
| | | | | | | The interactive bind tests work if the keys are treated like there is a human pressing them. This reverts commit 0006d23df82fd10c37acecc5a0fd578afb3be437.
* Disable the bind test for nowGravatar Fabian Homborg2015-10-18
| | | | | | | | | | This isn't pretty, but it fails for, as far as I can see, no _real_ reason. It doesn't seem to be possible to trigger the failure in real usage, no matter how fast you press the ESC key followed by something else. So now this is known and constant travis emails don't help it in any way.
* Tweak test runner to set up environment betterGravatar Kevin Ballard2014-11-24
| | | | | | Update the test runners so they set up their own environment in test_util.fish. This simplifies the Makefile and paves the way for adding utility functions for use in the tests themselves.
* Rewrite fishscript testrunner for better outputGravatar Kevin Ballard2014-10-02
| | | | | Update the fishscript testrunner to use the same output style as the interactive testrunner.
* Fix missing "1 test failed" lineGravatar Kevin Ballard2014-09-23
| | | | | | Also tweak colored output to reset before the newline instead of after, so travis behaves better (for some reason reset causes travis to display the line in black).
* Rejigger test suiteGravatar Kevin Ballard2014-09-23
| | | | | | | | | | Split test_interactive off from test_fishscript and add a new target test_high_level that tests both. Add some Makefile magic so the tests can be run serially without using sub-make, which gets rid of a little noise from the make output. Rewrite interactive tests to look better.
* Tweak interactive debug outputGravatar Kevin Ballard2014-09-19
|
* Dump interactive logs on travis test failureGravatar Kevin Ballard2014-09-19
| | | | | | | As far as I know we can't access the build artifacts from Travis, so we can't check the interactive logs after a test failure. Add an environment variable that causes the test runner to dump the logs itself, and set that variable for Travis.
* Reset fish_bind_mode when changing fish_key_bindingsGravatar Kevin Ballard2014-09-18
| | | | | | | Also avoid resetting bindings if fish_key_bindings is "modified" without actually changing. Fixes #1638.
* Add a test harness for interactive behaviorGravatar Kevin Ballard2014-09-07
Add a test harness that uses `expect` to drive Fish to test interactive behavior. Include some tests for `read`.