Hi
user
Admin Login:
Username:
Password:
Name:
Patterns for Testing Debian Packages
--client
debian
--show
debconf17
--room buzz 12436 --force
Next: 1 Fun with .buildinfo
show more...
Marks
Author(s):
Antonio Terceiro
Location
Buzz
Date
aug Tue 08
Days Raw Files
Start
18:00
First Raw Start
error-in-template
Duration
00:45:00
Offset
None
End
18:45
Last Raw End
Chapters
Total cuts_time
None min.
https://debconf17.debconf.org/talks/34/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Patterns_for_Testing_Debian_Packages.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
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
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
This talk is based in a paper I have published where I describe a pattern language (as in "design patterns") for automated software testing in production-like environments (a.k.a autopkgtest/DEP8 for us Debian people). The patterns describe common problems and solutions for testing Debian packages, and should be useful for maintainers willing to add tests to their packages.
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review