Results 1 to 6 of 6
Like Tree6Likes
  • 3 Post By Preemptive
  • 1 Post By Preemptive
  • 2 Post By Preemptive
  1.    #1  
    The webOS User Group exists to attempt to maintain legacy webOS devices for as long as is possible or practical. There will of course come a point where one or both of those conditions will cease to apply. The assumption is that LuneOS will by then be developed to a state where users can migrate to it, though there is no guarantee that the two situations will overlap!

    A few weeks ago at a group meeting, I suggested that a testing protocol for LuneOS could be developed so that users could better aid development. A testing checklist would be a step up from random 'playing' with a new release and would help the developers identify bugs and check the fixes and also of course to check new features. I imagine each new release might require specific tests additional to the standard routine.

    I'm not a LuneOS developer and there's been no formal feedback from the group on this idea, but a couple of developers have been positive. I don't have the expertise to suggest much beyond a few obvious user tests, but I'm posting this thread to see what happens. Ultimately, this will be a pointless exercise if webOS Ports don't at least endorse it and it will be most useful if they specify what tests will be most useful for them.

    I'll reserve a couple of posts below to list suggestions or webOS Ports can post here and I'll let them take the lead or link to their thread...

    So any suggestions for tests or various Quality Assurance type stuff? Post below.
    Last edited by Preemptive; 05/23/2019 at 09:23 AM.
    virox, Mutoidi and MudShark22 like this.
  2.    #2  
    The Following is a testing checklist by Tofe of WebOS Ports (original here).

    Possible Status Meaning
    OK Works fine
    Partial Works partially but is stable
    Unstable Crashes / freezes / glitches
    KO Not working, like previously
    REG Not working, but has been known to work
    N/A Not Applicable/Not Available
    ? Not tested / Don’t remember

    Flash / Sideload Installation.
    Boot LuneOS logo shows up.
    FirstUse app Content shows up.
    Widgets have LuneOS theme.
    Wifi selection works.
    Status bar and Gesture area shows up after firstuse app is finished.
    "Normal" UI after firstuse is ended.
    Virtual keyboard Shows up on focus.
    Disappears when focus lost.
    Language switch.
    Additional keys on long-press touch.
    Suggestions.
    Wifi Selection in system menu.
    Selection in preferences.
    On/off switch.
    Indicator.
    Keeps configuration between reboots.
    Bluetooth Selection in system menu.
    Selection in preferences.
    On/off switch.
    Indicator.
    Keeps configuration between reboots.
    Backlight On/off switch with Power key.
    Intensity with system menu.
    Gyroscope UI follows rotation.
    Rotation lock in system menu.
    Sound Boot startup sound.
    Vol+/Vol- on-screen indicator.
    Volume is actually adjusted.
    Telephony SIM operator in status bar.
    GSM signal strength in status bar.
    Call a number.
    Receive call.
    SMS Send SMS.
    Receive SMS.
    Compositor Switch card view / maximized card.
    Card view : Horizontal scroll.
    Discard card with swipe up.
    Stack cards.
    App name is shown when card maximized.
    Gesture Area Swipe up or tap to go to card view.
    Swipe left ( « back » ).
    Swipe right to take screenshot.
    Testr GPS.
    Banners.
    Apps QML Apps (Browser, Phone apps).
    Enyo Apps (Messages, Maps…).
    JustType shows up and search works.
    Last edited by Preemptive; 05/11/2019 at 02:14 PM.
    MudShark22 likes this.
  3.    #4  
    Tofe has given permission for a checklist to be posted here (see above). I think this makes a pretty good set of tests to begin with and anyone is welcome to suggest additions on this thread.
    MudShark22 and Shuswap like this.
  4. #5  
    So...for formality sake...
    Table / Reports in this thread?
    Thread by device?
    Thread by device and release?

    If there was voting I would vote Thread by Device, table should denote release/version.

    Will reinstall Doppio for Mako now.
    And try another device too.

    - T

    Sent from my ONEPLUS 5t awaiting LuneOS
    This space for rent or lease. Inquire within.
  5.    #6  
    Quote Originally Posted by MudShark22 View Post
    So...for formality sake...
    Table / Reports in this thread?
    Thread by device?
    Thread by device and release?

    If there was voting I would vote Thread by Device, table should denote release/version.

    Will reinstall Doppio for Mako now.
    And try another device too.

    - T

    Sent from my ONEPLUS 5t awaiting LuneOS
    This is not a reporting thread. It is a thread to develop a protocol for user testing. It makes sense to take a lead on that from the actual developers, but the people here are long-time webOS users, some with their own development experience, so we could propose additional tests or more in depth tests or individuals could have specific use-cases that could find obscure bugs. It's up to the ports team if they formally adopt any additional suggestions here, but up to us what we think is useful.

    In any event, reporting can be done in a number of ways. There is the official reporting system: https://webos-ports.org/wiki/Bug_Report_guidelines The bug tracking system appears to be down at the moment, but I think I've seen stuff on the logs that this will either be fixed or replaced. You can still report bugs on each release thread. At this point, I doubt there are so many of us that it is worth sub-dividing by device, but there's nothing to stop people from doing that - especially if a device is notably different that there may be significant difference in the issues - like a tablet or some IoT device.

    Support (not so much bug reports) can be asked for on the IRC channel. Feature requests are at the discretion of the developers, so joining the team is the best way to get your idea in there.

    Note that at this point, developers will be doing these tests, but may only do them once or twice (e.g. after a reboot). Users testing stable releases (or even unstable) may spend more time with a release (rather than working on it) and identify more subtle bugs. That's really the idea here: To help the developers by widening the pool of testers and formalising the testing process. Of course, QA testing also includes doing loads of crazy things to attempt to deliberately 'break' the system. I don't see why we couldn't add those types of tests also.

    I'd suggest putting the table into a spreadsheet and tracking your notes for each release across columns as it is on the website version - yes, maybe a page per device if you have more than one type, but others may have better suggestions.

    But to reiterate: This thread is about testing. There are already places for reporting and it's best to send bug reports directly to the webOS Ports bug-tracker or to the release threads that they will monitor.
    Last edited by Preemptive; 05/13/2019 at 01:24 PM.

Similar Threads

  1. pivotce: LuneOS November Stable Release: Doppio
    By webOS Ports in forum LuneOS
    Replies: 59
    Last Post: 03/16/2019, 03:46 AM
  2. LuneOS: Mi A1(tissot) installation truble
    By rapitfly in forum LuneOS
    Replies: 10
    Last Post: 12/03/2018, 12:57 PM
  3. LuneOS on Maguro don't boot up
    By davodego in forum LuneOS
    Replies: 7
    Last Post: 08/15/2018, 10:47 PM
  4. Help installing luneos
    By Devbecca in forum LuneOS
    Replies: 0
    Last Post: 05/26/2018, 07:05 PM
  5. LuneOS smart watch ?
    By Firepower in forum LuneOS
    Replies: 1
    Last Post: 05/26/2018, 03:56 AM

Tags for this Thread

Posting Permissions