veyepar: Automated acceptance tests for terminal applications

Author(s):	Roman Joost
Location	Room 7
Date	jan Wed 15	Days Raw Files
Start	10:45	First Raw Start	error-in-template
Duration	0:45:0	Offset	None
End	11:30	Last Raw End
Chapters
Total cuts_time	None min.

https://lca2020.linux.org.au/schedule/presentation/63/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Automated_acceptance_tests_for_terminal_applications.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Acceptance testing is a method of testing an application from a users point of view. In this talk, I will demonstrate our approach to full automated testing a terminal email application (purebred) with the tasty-tmux framework. I'll elaborate the benefits and trade-off's, what problems we experienced and how we solved them.

Automating acceptance testing is challenging, because the tests can not adapt to timing sensitive changes in the application. This causes random failures and unresponsiveness. The longer these problems are ignored, the longer value diminishes and investment increases for workarounds and fixes.

The audience will get a better understand of what it takes to automate timing sensitive tests. The concept, problems and solutions are language agnostic applicable to any terminal platform and application.

Project URL: https://github.com/purebred-mua/tasty-tmux

Talk Outline:

What is acceptance testing and why should you automate it
    What other choices of testing did we have and why we haven't chosen them
    The effort we put into automating our tests
    What we gained with automating our acceptance tests
    Future ideas

Comment:

production notes