@wxl mentioned testcases; so I queried "Replace a partition" using Calamares text; I've opted to add a test rather than modify the "Replace a partition" as it really tested for something different (in my mind anyway).

Neyder noted (#lubuntu-devel) that the LIVE test case mentions Ubiquity & has references to picking timezone.... prior to "Try FAMILY"

To me they were ready Sept 24, however https://code.launchpad.net/~guiverc/ubuntu-manual-tests/lubuntu-calamares shows

'people' names committed - READY FOR REVIEW please. @wxl @tsimonq2

no issues at all with 'rough draft', thought it looked very polished

@tsimonq2 or @wxl - the existing test cases all have a number (eg. I've based mine on 1701 for new installs, and 1310 for upgrades). What numbers shall I give them? or where do I get the numbers? (or can it be any unused number?, isn't there a some document/procedure for claiming numbers?)

I have also committed the TUI (text user interface) upgrade
Please note: There have been no changes since 1-Sept-2019's comment & diff

As I wrongly wrote on D43, booted 19.10 daily (2019-09-13) on

• sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT)
• hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

Check if meta+r opens runner.
Check if pressing search key opens runner.
Check if Ctrl+Alt+B opens browser.
Check if pressing Homepage key opens browser.

In T21#2311, @wxl wrote:

@tsimonq2, (I was supposed to mention @ standup but i had my usual *blank/empty mind* at meeting)..

@tsimonq2 I'm stuck with GUI upgrade..

Do you want TUI & GUI release-upgrade testcases also on iso.qa...?
I don't recall seeing them for any other flavor, though I have found http://iso.qa.ubuntu.com/qatracker/testcases/1310/info which IS used by Ubuntu Budgie and appears with their other tests as a 'run-once'.

• Pushed [bazaar] & merge request done thru launchpad

I can't currently login to notes.lubuntu.me so I'll flood-post here (delete or move if it's a problem)

It doesn't view very well now, but my 'reply' was based on P38 with a Y/N placed before each. Yep=worked, Nah=no.

New 19.10 install (2019-08-26 daily), on dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
(I have apt-get installed clementine so I could have music play in background) & changed monitor-settings (swapped left-right & my-right display is portrait-left)

I'm playing with wxl/testy compton, and noted a

My testing results are :-

I don't believe anything shows any differently for secure+EFI boot, (vs efi) so it'll use identical testcases as EFI.

In T56#2000, @wxl wrote:

...

Therefore, I believe the testcase should provide instructions to:

• Check to see if the target drive has any mounted partitions
• Unmount any partitions if found

…before launching the installer.

I just booted [19.10] daily on vaiocrap & noticed an OEM option at grub; maybe we should have testcase(s) for that??
(i'm starting EFI set)

They will be new testcases; the files currently are all local (diffs online were a form of backup, though created at that point as I wanted two to speed creation of the fourth one via copy/paste); I haven't yet done the vm install to verify fourth is good. I don't yet understand the upload steps which is why they're all local - but I'll/we'll get there.

Thanks Walter & Dan too.

:) I didn't think of swap, and that would apply to all systems I tested on.
and easy to deal with in a text line; I'm thinking we ask testers to leave a comment on that one

https://paste.ubuntu.com/p/Cvvx77Gv5r/
has the ~/.cache/Calamares/session.log file.
I hadn't exited the installer at that stage, it was grabbed when it was at the

• install alongside
• replace partition
• manual partitioning

question, ie. no erase disk & install option provided. Single 80gb disk; partitions for /, swap & /home only

Our current (testcase 1701) is written for "Erase Disk" however it doesn't always show.

On hp dx6120 using Lubuntu 19.04 x86

I ran the installer a few times & made notes (largely a comparison between 19.10's install and the manual), right now I have no idea where those notes are (pad.ubuntu.com as I recall, but i'll have to find the email or whatever breadcrumb I left for myself to locate it). I also downloaded existing testcases and then looked at alternate editors as I felt my usual editor would be error prone (I didn't like how it appeared).

Opened k3b & created a favorites.k3b file with some my local mp3 directory (data project). Exited k3b.
Using pcmanfm-qt found the favorites.k3b file, it opened correctly in k3b

Your response got a HUGE howl of laughter when I read it @apt-ghetto, followed very quickly by the reddest face possible....

• Testing MAGNET LINKS (note: done on two boxes; d780 [upgraded last fri-sat] & d960 [fulyl-upgraded]

There's also an equally [*bad but quick*] Software image added to https://wiki.ubuntu.com/Lubuntu/Marketing/Lenny (Lubuntu modern logo overlayed on top of old LXDE symbol)

19.10 daily [2019-07-18] with -proposed calamares 3.2.11 installed, install using 'manual-partitioning' into partition (no encryption) flawless (default american english unchanged on first language choice)
19.10 daily [2019-07-18] with -proposed calamares 3.2.11 installed, install using 'replace-partition' into partition (no encryption) flawless (switched to british-english on first language choice)
19.10 daily [2019-07-18] with -proposed calamares 3.2.11 installed, install using 'replace-partition' into partition (encryption), british-english chosen first language choice, prior to booting this I rebooted into live & looked at hdd, luks partition where installed should be; I tried wrong passwords & couldn't access. I booted hdd with wrong passwords, unable to get in, final boot using correct password & was in; all looks good.

1280x800 (16:10) j3400 ; host 18.04 LTS but I didn't change GRUB_DISTRIBUTOR line so no logo

I just had a really good QA-test using 19.10 daily.
(following bits copied from my comments on test)

@The_LoudSpeaker as requested via irc

With changes made as requested by @apt-ghetto - fyi: d780 & I stopped timer to find my phone

Tested on vaio (uefi) & looks good. (for some reason it's grub is reporting 19.04; a qa-test 19.10 install pre-release and I don't know why, but it's my only uefi box and I hadn't noticed this before).

Quick Note: Whilst I'm too slow for useful testing, I have noted the https://manual.lubuntu.me/F/keyboard_shortcuts.html as it stands now will require change, eg. S-A-Left|Right no longer do the SendToDesktopToLeft ...

FYI: Sorry I should have responded months ago (I'm very forgetful), but the smallest screen I can find is 1024x768 for actual hardware testing (according to online specs)

Lubuntu 18.04 owns the MBR so it's run in lubuntu at term (sudo update-grub)..

I made it so d755 doesn't see opensuse during update-grub (easy; it only seems to see it if btrfs partition is mounted) & re-ran update-grub and rebooted. Options are Ubuntu, Advanced.., Memtest, Memtest.., wNT/2000/xp alas no bird-logo is there

I didn't notice the humming bird logo on any sorry; looking back on it's there for vaio (uefi), but not on bios d755, d780 or dx6120 (I didn't look on d960 as I'm using it!), but Yes I do have multiple installs of *nix on all except vaio (d755 has ubuntu & opensuse leap; others have multiple versions of Ubuntu).

From what I can see all are set gfxmode=auto (in /boot/grub/grub.cfg) with #GRUB_GFXMODE= lines all commented out in /etc/default/grub which I believe to be defaults.

tested on machine (specs), arch, bios|eufi, host (lubuntu)

I've watched the sony vaio ultracrap using the installed up-to-date 19.10 system, but have not noticed any issues with battery condition drop. The device mostly sits unused with occasional checks of battery status, or less occasional use as I dislike the keyboard+touchpad.

my lubuntu iso was updating (19.10 daily now) so booted
https://cdimage.debian.org/mirror/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-lxqt.iso [2019-04-22 06:17] on my lenovo thinkpad sl510 (c2d-t6570, 2gb ram, i915), it showed battery at 38% and [somewhat slowly] dropping as I played .. 37% .. 36% (I also had 'battery.info' screen open as it's easier to read), then i closed the battery.info window, and it seemed to stay at 36% for longer than I expected, ... then after a long while I noticed the change to red battery and it was 9% -- i don't believe it was me forgetting to watch battery drop.. (but it could be battery.health issue or yes i lost-track-of-time..)