pep8 again!
utf-8 decoding is a bad move, use latin1!

I feel very strongly about this, and I've provided evidence for keyboard input, but it goes also for keyboard output. utf-8 would seem safe, but it isn't: https://gist.github.com/jquast/5649654

Now that I'm testing terminals such as 'kermit' and 'avatar', which use binary-packed values (say, '\xff' to indicate column 233 as opposed to the number '233'), these will raise a UnicodeDecodeError, "invalid start byte".

If you don't believe me, try kind='kermit' or kind='avatar', along with t.cup(n, n).

latin1 (iso8859-1), on the other hand, does not modify these 8-bit bytes at all, leaving them as-is.
pass term= keyword to sequence wrap explicitly
implement terminal-relative sequence-awareness
test additional terminal kinds
only test *supported* sequences per each terminal
raw terminal codes not supported.
pep8, cleanup, brevity, docfix
remove elongated tests

now, a sequence such as 't.normal' that emits multiple sequences is understood as only a single sequence by blessings.
do not strip() strings containing sequences

some binary-packed terminals may provide ' ' as an indicator of color/attribute, which is removed when strip() is used.
only test cvvis if supported