What is a Lubuntu 'Live Session' test

Documentation
4

Common tasks I perform in live testing

  • firefox; stream local news in window, maximized & using f11 & fullscreen on each display of box (I assume most users will do this on their machines sometime). This is often left running in the background as I work on my primary box… allowing a check that the screensaver will kick-in etc
  • drag windows around, maximize, minimize, tile & what I call general user play (we’ll all do this differently, but I treat it as if it were my main box at times, other tests do things I’d never do)
  • change look, appearance, openbox settings (more user type play) to something more like what I have, or more commonly something very unlike what I use, add or change panel etc
  • using the file manager (pcmanfm-qt) navigate to an installed user directory on the box, and open found files using installed apps (ie. txt, pdf, mp3, avi, odt, ods or whatever other files I find locally).
  • I also have a directory of test files that I open if it exists on the machine, it’s available on a network share (NFS so it requires nfs-common to be added, but I’ll scp it to the live session if I want but usually use whatever’s on the box). The files are just random assortment of txt, pdf, mp3, odt, mkv etc
  • create at terminal, or edit a text file that will be just text (CSV format for calc), which I can then ‘import’ into libreoffice calc/writer (if created in featherpad, I usually leave it open), if it imports correctly :slight_smile: so then I make changes & save that (to a new file), perusing later from terminal to ensure results are good (view contents, file etc responds appropriately…). The reason for leaving featherpad open, is if I re-write the changes featherpad gives a nice warning that the file contents have changed :slight_smile:
  • if laptop, connect charging cable & monitor for changes in panel icon, disconnect charging cable etc… Monitor the battery indicator during the test, looking for it to discharge/charge appropriately for that laptop (laptops will respond differently, as will batteries be they healthy/average/poor etc)
  • volume media keys work, switching workspaces, brightness keys work; these are mostly upstream kernel functions (not Lubuntu specific) but if they stop working on all boxes it maybe a specific Lubuntu issue
  • open muon & pick a random package, install & test it opens
  • open discover & pick a random package, install & test it opens/runs
  • I only run through all menu items occasionally, if I’m not doing that today I just select random apps and open. On these days I try and operate the app a little (if it’s libre office writer for example, type some text, make some characters bold, change fonts etc), save the file, then at terminal inspect the file is what I consider it should be (viewing contents, file etc), close & re-open app and have it re-open the file
  • on some boxes I suspend, (wait ~15 secs) & resume the live session, but many uEFI boxes don’t allow this, so you have to know your box will allow this to function before you use it.
    …

These are just a few examples.

it’s best if you have your own files, or even better, your own methods of testing; more appropriate to what you think a real user (ie. you) would do. We all use our systems differently, so your testing should reflect how you use a computer :slight_smile:

3 Likes