Completed
PREVENTATIVE MEASURES
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Automated Acceptance Tests for Terminal Applications
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Terminology Motivation • What is the Test Framework • Pitfalls
- 3 ACCEPTANCE TESTING • Test whether the system/feature fullfills it's acceptance criteria • testing from the users point of view (e.g, user stories) can be any type (unit-, integration-, system tests)
- 4 HOW IS THE TESTING CARRIED OUT? Manual vs Automated • Humans are very good at finding outliers or differences • automated is "infinitely" repeatable and fast
- 5 ACCEPTANCE TESTING TERMINAL APPLICATIONS Selenium doesn't exist for terminal applications • support for command line interface apps, but less for text UIS
- 6 UNIT TESTING THE TERMINAL APPLICATION UI usually straight forward for parts
- 7 HOW DO WE USE TMUX FOR TESTING
- 8 PREVENTATIVE MEASURES
- 9 PROTOCOL OCCURRENCE OF RANDOM FAILURES
- 10 HAVE CI RUN ALL TESTS BEFORE MERGE
- 11 TIME TO DEBUG FAILURES improves debugging skills of your engineers better ability to reason out a complex system
- 12 CONFIDENCE THAT THE PULL REQUEST DOES NOT REGRESS THE APPLICATION BEHAVIOUR
