================================
BoF: autopkgtest skills exchange
================================

autopkgtest resources
---------------------

* /usr/share/autopkgtest/doc/
* http://ci.debian.net/doc/
* Debconf15 talk (Tutorial: Functional testing of Debian packages)
  * WIP: transcription by Brandon Fairchild, to be added to ci.debian.net/doc/
* WIP: functional testing patterns paper

contact:
	#debci @ OFTC
	autopkgtest-devel@lists.alioth.debian.org
	debian-qa@lists.debian.org

Things we might want to talk about
----------------------------------

* autopkgtest/ci.debian.net feedback
* doubts/questions on how to declare/run test suites
* interesting testing tools
* interesting testing techniques

Session Notes
-------------


Questions
---------
* Does autopkgtest support tests that require network (more than localhost)?
  * dbconfig-common password detection running over the network.
  * no restriction on either debian or ubuntu
  * idea: declare that you need network in the spec (#801895)
* block testing migration?
  - needs to ensure that packages do not get blocked from running tests on
    updated sources.
  - Britney file needs improvement (elbrus wants to look into this)
  - release goal for buster?
* Is it allowed or suitable to add debian/tests to packages for {old,}stable suites?
* ^^ and can ci.debian.net run stable tests?
	with backports support...
	YES! PLEASE HELP
* default adt-run currently uses null, could use QEMU
* log output X artifacts ($ADT_ARTIFACTS)
* kde-jenkins repository - parses autopkgtest output and generates a JUnit format (for jenkins etc)

how to help
-----------

  * run debci locally and hack on it
  * talk to terceiro
  * look at the BTS
  * send patches
  
  (we'll form a team, stay tuned. subscribe here if you want to be part of it)
  * elbrus
  * nicoo (nicolas@braud-santoni.eu)
  
INTERESTING TEST SUITES TO LOOK AT
----------------------------------

  * cacti   - recursive wget against a webapp
  * systemd - setups init, reboots, tests that basic services come back
  
INTERESTING TOOLS TO LOOK AT
----------------------------
  
  * clitest - copy-and-paste terminal sessions into test suites
  * sikulix (experimental) - test tool for GUI applications
  * using the dbus.accessibility bus to test graphical packages
    (and confirm accessibility at the same time), done by GNOME
    https://thegnomejournal.wordpress.com/2009/11/06/gnome-desktop-testing-automation-and-how-to-use-mago/
  
IDEAS/WISHLIST FOR AUTOPKGTEST
------------------------------

  * use a given virt -- say qemu -- backend by default
  * offer to automatically create testbed if none is found
  * remember the virt backend the user usually uses
  * print a warning if there is no explicit debian/tests/control and autodep8 is not installed
  * detect error message from log and display that
  * produce output formats that others tools can use
    (https://anonscm.debian.org/cgit/pkg-kde/pkg-kde-jenkins.git/tree/scripts/adt2junit.py)