Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@rolandwalker
Copy link
Contributor

@rolandwalker rolandwalker commented Aug 23, 2017

Summary

keystrokes                 ':none'
keystrokes -append -keysym 'Enter'
keystrokes -append         ':quit'
keystrokes -append -keysym 'Enter'
# or keystrokes ':none\r:quit\r'

test_tig

assert…

Further documented in test/README.adoc test/API.adoc.

This is in reasonably functional form but is a WIP in part because it will merge conflict with several other outstanding PRs. This is in functional form and merge conflicts have been resolved.

Another interesting approach to simulating input is driving tig inside of tmux as in

this has the advantage that the screen-capture action can be done by tmux. Though leveraging that would likely mean changing all existing tests.

@rolandwalker rolandwalker force-pushed the simulated-keystrokes branch 4 times, most recently from f8d83c7 to 749c3c4 Compare August 24, 2017 12:22
@rolandwalker rolandwalker force-pushed the simulated-keystrokes branch 2 times, most recently from 8b8091c to 8dab39b Compare May 21, 2018 23:05
and preserve a connection between input window (status_win) and tty.

Ncurses fails to initialize in the usual way unless the args to newterm
are both ttys.
and generalize for any other executable requirements
needed for keystroke-stuffer
since it works by setting an environment variable.  Logically perhaps
all items should be in the subshell.
needed for valgrind to work with simulated keystrokes
 * keystrokes()
 * test_case -keystrokes
 * TEST_OPTS='trace_keys'
 * docs
simulated keys can work around the inability of scripts to run other scripts
@rolandwalker rolandwalker force-pushed the simulated-keystrokes branch from 8dab39b to a087e81 Compare May 24, 2018 12:24
@rolandwalker rolandwalker changed the title WIP simulated keystrokes in test suite simulated keystrokes in test suite May 24, 2018
@rolandwalker
Copy link
Contributor Author

Now that tig is the process-group leader this PR is more focused and can be evaluated on its own.

I suspect that you won't like the added complexity and the python requirement (though keystroke test are skipped without python.)

But it was fun to do in any case. The motivation was to provide test coverage to some hidden corners that libtest scripts could not reach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant