cac99271ca
Move lib variable to do_terminal_tests
2017-04-30 14:42:54 +03:00
255ff49def
Define tests via dictionaries, do not hardcode row number
2017-04-30 14:36:50 +03:00
1b3aacb837
Move most of the vterm testing code to tests.lib.terminal
2017-04-30 13:18:50 +03:00
e34a372f10
Fix number of spaces
2017-04-30 12:21:46 +03:00
e3d0649372
Always remove all tmux logs
2017-04-30 06:40:05 +03:00
93cbeb92e9
Fix misplaced lines
2017-04-30 05:35:53 +03:00
bbb9ae21f4
Move printing tmux logs out of test_expected_result
2017-04-30 05:34:19 +03:00
883aa73e9f
Refactor vterm tests: move most of things out of the try
2017-04-30 05:31:14 +03:00
519f08541b
Also move arguments list out of the try body
2017-04-30 05:07:25 +03:00
3d0f168806
Refactor try block in main and refactor specifying dimensions
2017-04-30 05:05:32 +03:00
4c2583311c
Do not make build successfull if only second test was successfull
2017-04-30 05:05:30 +03:00
32eec2f9f3
Rename expected_result_new to expected_result_1_8
2017-04-30 05:05:30 +03:00
756ea5bfab
Still try to kill server, just now not allow exceptions to fail build
2017-04-30 05:05:29 +03:00
86f6943b08
Unlink in place of appending x
2017-04-30 05:05:29 +03:00
b93ae8e8a2
Do not reuse existing socket paths
2017-04-30 05:05:28 +03:00
e19feb9472
Use different socket for each attempt
2017-04-30 05:05:28 +03:00
b71d5f2d44
Do not bother with issuing kill-server, simply -KILL tmux
2017-04-30 05:05:27 +03:00
36b9c966e0
Use absolute path for -S
...
It appears that using relative path for -S is not the best idea and yields tmux
calls from powerline-config not working.
2017-04-30 05:05:26 +03:00
908d767ec0
Give a name to tmux default statusline color
2017-04-30 05:05:25 +03:00
b7a46eb7a8
Give some colors names
2017-04-30 05:05:24 +03:00
4a3f098f22
Use powerline.conf as it is supposed to be used
2017-04-30 05:05:22 +03:00
fb769d7297
Refactor environment and expected results
2017-04-30 05:04:35 +03:00
14982fc693
Make tmux tests more sane
2017-04-30 01:38:59 +03:00
eeaaf3930f
updating tmux tests to expect window_flags in window status format
2015-08-27 09:05:13 +01:00
9f0665506b
Rename …/test_in_vterm/test.sh to …/test_in_vterm/test_tmux.sh
2015-08-21 18:40:49 +03:00
a718a10591
Add integration tests for tmux segment truncation
2015-05-23 16:11:08 +03:00
424d71ee57
Use different string for tmux-2.0
2015-05-10 15:33:43 +03:00
bb6342c12a
Tell tmux correct path to shell to use
2015-02-21 15:59:10 +03:00
d53c780071
Do not use absolute path for tmux socket
...
Absolute path is too long when using tests in ebuild.
2015-02-21 15:59:10 +03:00
e6b3bff50a
Rerun main() only after running finally block
2015-02-21 04:35:56 +03:00
0a0af212ad
Allow specifying path to libvterm from environment
...
Uses POWERLINE_LIBVTERM environment variable.
2015-02-20 23:48:26 +03:00
8629999379
Make sure that it is possible to use “system” libvterm.so
2015-02-20 23:47:18 +03:00
feb9a57dc0
Move code that prints tmux logs to test_tmux.py
2015-02-19 11:39:12 +03:00
f8ba6b021c
Restart failed tmux vterm test a few times
2015-02-19 11:39:12 +03:00
66c6128b66
Wait less in vterm tmux tests
2015-02-07 11:14:09 +03:00
92d4beffa4
Wait more before failing tmux vterm tests
...
May fix random test failures.
2015-02-07 05:00:37 +03:00
71322dfe5b
Use st-256color terminal for tests
...
Reasoning:
1. vt* TERMs (used to be vt100 here) make tmux-1.9 use different and identical
colors for inactive windows. This is not like tmux-1.6: foreground color is
different from separator color and equal to (0, 102, 153) for some reason
(separator has correct color). tmux-1.8 is fine, so are older versions
(though tmux-1.6 and tmux-1.7 do not have highlighting for previously active
window) and my system tmux-1.9a.
2. screen, xterm and some other non-256color terminals both have the same issue
and make libvterm emit complains like `Unhandled CSI SGR 3231`.
3. screen-256color, xterm-256color and other -256color terminals make libvterm
emit complains about unhandled escapes to stderr.
4. `st-256color` does not have any of the above problems, but it may be not
present on the target system because it is installed with x11-terms/st and
not with sys-libs/ncurses.
For the given reasons decision was made: to fix tmux-1.9 tests and not make
libvterm emit any data to stderr st-256color $TERM should be used, up until
libvterm has its own terminfo database entry (if it ever will). To make sure
that relevant terminfo entry is present on the target system it should be
distributed with powerline test package. To make distribution not require
modifying anything outside of powerline test directory TERMINFO variable is set.
2015-01-18 05:15:47 +03:00
71d7e3921f
Also supply LD_LIBRARY_PATH when killing server
2015-01-18 03:50:12 +03:00
6f6c466bc3
Make sure LD_LIBRARY_PATH and PYTHONPATH are exported
...
LD_LIBRARY_PATH is required for UCS2 CPython versions.
2015-01-17 00:41:28 +03:00
1e25c5ec42
After failing tmux vterm tests run powerline-config
...
Its output may give some clue.
2015-01-17 00:26:12 +03:00
a0edcccecf
Increase sleeping time
...
It appears that just one second is not enough for travis
2015-01-17 00:26:12 +03:00
44273f299b
Do not print the whole screen unles something went wrong
2015-01-17 00:26:12 +03:00
faef4585b2
Add support for old tmux versions in tests
...
Tmux-1.6 does not have special highlighting for previously active window. Other
then that view is identical.
2015-01-17 00:26:12 +03:00
9db1e7b76e
Use tmux executable from fake PATH for running tmux
...
Otherwise with system tmux present it may appear that subprocess.check_call will
use it instead.
2015-01-17 00:26:11 +03:00
93acec238e
Create vterm-based tests that will test tmux support
...
It is possible that they eventually will be used also for shells: at least this
makes using postproc.py with all its hacks not needed.
2015-01-17 00:26:11 +03:00
Foo
Sergei Trofimov