Description
An automatable terminal session with send/expect controls.
This package leverages the
go-expect package to test
terminal applications on Linux, MacOS and Windows, which has been forked from
Netflix/go-expect
It has been developed for CI testing of the ActiveState state
tool
termtest alternatives and similar packages
Based on the "Command Line" category.
Alternatively, view termtest alternatives based on common mentions on social networks and blogs.
-
Rich Interactive Widgets for Terminal UIs
Rich interactive widgets for terminal-based UIs written in Go -
tcell
Tcell is an alternate terminal package, similar in some ways to termbox, but better in others. -
The Platinum Searcher
A code search tool similar to ack and the_silver_searcher(ag). It supports multi platforms and multi encodings. -
readline
A pure golang implementation that provide most of features in GNU-Readline under MIT license. -
asciigraph
Go package to make lightweight ASCII line graph ╭┈╯ in command line apps with no other dependencies. -
CLI Color
Terminal color rendering tool library, support 8/16 colors, 256 colors, RGB color rendering output, compatible with Windows. -
mow.cli
A Go library for building CLI applications with sophisticated flag and argument parsing and validation. -
termtables
A Go port of the Ruby library terminal-tables for simple ASCII table generation as well as providing markdown and HTML output -
tabular
Print ASCII tables from command line utilities without the need to pass large sets of data to the API.
Get performance insights in less than 4 minutes
Do you think we are missing an alternative of termtest or a related project?
Popular Comparisons
|
SaaSHub - Software Alternatives and Reviews
Sponsored
www.saashub.com
|
README
termtest
An automatable terminal session with send/expect controls.
This package leverages the go-expect package to test terminal applications on Linux, MacOS and Windows, which has been forked from Netflix/go-expect
It has been developed for CI testing of the ActiveState state tool
Example usage
import (
"testing"
"github.com/ActiveState/termtest"
"github.com/stretchr/testify/suite"
)
func TestBash(t *testing.T) {
opts := termtest.Options{
CmdName: "/bin/bash",
}
cp, err := termtest.NewTest(t, opts)
require.NoError(t, err, "create console process")
defer cp.Close()
cp.SendLine("echo hello world")
cp.Expect("hello world")
cp.SendLine("exit")
cp.ExpectExitCode(0)
}
Multi-line matching
After each bytes termtest receives from the pseudo-terminal output, it updates the state of the virtual terminal like a terminal user would see it (including a scroll back buffer if necessary). The Expect() look for matches in this processed output. Of course, the terminal wraps its output after text gets longer than 80 columns (or whatever width you have configured for your terminal). As this makes it more difficult to match long string, the default Expect() removes all these automatic wraps.
Consider the following examples, that all assume a terminal width of 10 columns.
Programme sends a line with more than 10 characters
- Programme sends string "0123456789012345".
- Terminal output is "0123456789\n012345 \n".
cp.Expect("0123456789012345") // this matches
Programme sends several lines separated by \n
- Programme sends string "line 1\nline 2\n".
- Terminal output is "line 1 \nline 2 \n".
- The following does NOT match:
cp.Expect("line 1\nline 2\n") // this does NOT match - The following does MATCH:
cp.Expect("line 1") cp.Expect("line 2") - The following does MATCH:
cp.Expect("line 1 line 2 ")
Custom matchers
Custom matchers that match against either the raw / or processed pseudo-terminal output can be specified in the go-expect package. See expect_opt.go for examples.