Pre Release Testing

#Full Test

Applies to: Core

##Live boot and install to hard drive

• create new VM
• check that core boots in live mode
• reboot
• check that core installs to hard drive
• reboot
• check that install to hard drive works

##Confconsole

• Loads after boot, shows TKLBAM not initialized

• Network configuration works (DHCP + Static IP)

  • Set DNS to 8.8.8.8, check /etc/network/interfaces

##Console sysinfo

• test (as per below)

$ ssh testcore

Welcome to Core, TurnKey Linux GNU/Linux 14.1 / Debian 8.4 Jessie

  System information (as of Wed Jan 18 06:40:28 2017)

    System load:  0.00             Memory usage:  2%
    Processes:    76               Swap usage:    0%
    Usage of /:   5.0% of 29.40GB  IP address for eth0:  192.168.1.20

  TKLBAM (Backup and Migration):  NOT INITIALIZED

    To initialize TKLBAM, run the "tklbam-init" command to link this
    system to your TurnKey Hub account. For details see the man page or
    go to:

        http://www.turnkeylinux.org/tklbam

##Authentication

• log into console with root password
• log into webmin with root password
• log into webshell with root password

##Service authentication

Applies to: LAMP LAPP Nodejs Tomcat Domain-Controller Fileserver

• log into web app (where relevant)
• log into Adminer
• test/log into others... (see confconsole services per appliance)

##TKLBAM

Applies to: LAMP (could be tested on any - but LAMP an ideal option)

• install LAMP to VM
• add test data as per below

  adduser alon

  echo test > /root/test
  chown alon:alon /root/test

###console cli - initialization

• Initialize TKLBAM

tklbam-init APIKEY

###console cli - "dry run" backup

tklbam-backup --simulate

• examine /TKLBAM/fsdelta-olist

  • it should be empty (or close to it), since there is no delta!

• examine /var/lib/tklbam/profile/dirindex

  • file paths shouldn't have any weird prefix in them

###console cli - "wet run" backup

tklbam-backup

• TotalDestinationSizeChange should be about 10KB

###console cli - restore

• install 2nd LAMP VM (1st can be destroyed)

tklbam-init APIKEY tklbam-list

• shows TESTBACKUPID

tklbam-restore TESTBACKPID

• check /root/test exists and is owned by alon:alon

• examine /var/log/tklbam-restore, make sure no error messages

tklbam-restore-rollback

• /root/test gone
• user alon in /etc/passwd gone

###Webmin - initialization

• initialize tklbam

###Webmin - backup

• download escrow key

• enable daily backups: yes

  • check /etc/cron.daily/tklbam-backup is +x

• enable daily backups: no

  • check /etc/cron.daily/tklbam-backup is -x

• change size of backup volume to 45 MBs

  • check /etc/tklbam/conf includes change

• change frequency of full backups to 1M

  • check /etc/tklbam/conf includes change

• add override: -/etc/.git

  • check /etc/tklbam/overrides includes change

• local simulation (/etc/.git)

• backup

  • set passphrase
  • check that Passphrase field updated on the Hub

###Webmin - restore

• install 3rd LAMP VM (1st & 2nd can be destroyed)

• Initialize TKLBAM (via Webmin)

• Restore most recent backup (from previous Webmin backup)

  • Confirm asks for passphrase (it should because we've set one!)

#Additional Tests Applies to: all remaining appliances

• username &/or email set by inithook (where relevant)
• domain set by inithook (where relevant)
• password set by inithook (where relevant)
• web app is running, and:
  • secure (i.e. need to login prior to any level of access)
    • note framework apps are an exception to this rule
  • available via http
  • available via https
  • login credentials (entered via inithooks) enable login (where relevant)
• webapp appears to be displaying correctly (e.g. css applied):
  • without login:
    • via http
    • via https
  • logged in
    • via http
    • via https