https://bugs.winehq.org/show_bug.cgi?id=44351
Bug ID: 44351 Summary: [Feature Request] Test Result Draft Product: WineHQ Apps Database Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: appdb-unknown Assignee: wine-bugs@winehq.org Reporter: asembus@gmail.com Distribution: ---
i thought it would be nice to have test result draft system in appdb just like in blog service. Why ? because IMO testing an app need a lot of *click and some misclick will deliver me to another page and lost all my progress. and sometime where i don't have stable internet to test a game i would like try every offline feature first and test it again when i got more reliable connection.
Thank you for keep working on this awesome project.
https://bugs.winehq.org/show_bug.cgi?id=44351
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- What exactly do you mean by "Test Result Draft"?
https://bugs.winehq.org/show_bug.cgi?id=44351
--- Comment #2 from Rosanne DiMesio dimesio@earthlink.net --- The idea is to have a way to save an unfinished version of a test report and be able to come back later and finish it. It's not necessarily a bad idea, though not a high priority for me. It would need a time limit on how long a draft would be kept so we don't end up storing a massive number of incomplete test reports that users have forgotten they started.
https://bugs.winehq.org/show_bug.cgi?id=44351
mrdeathjr28@yahoo.es changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28@yahoo.es
https://bugs.winehq.org/show_bug.cgi?id=44351
--- Comment #3 from mrdeathjr28@yahoo.es --- (In reply to Rosanne DiMesio from comment #2)
The idea is to have a way to save an unfinished version of a test report and be able to come back later and finish it. It's not necessarily a bad idea, though not a high priority for me. It would need a time limit on how long a draft would be kept so we don't end up storing a massive number of incomplete test reports that users have forgotten they started.
Hi another interesting idea could be make same options for select for example cpu - mount of ram - driver version
Example this field can be feed with user provide information: example user select existing cpu example intel core i3 6100 and other can add for example core i3 8350K overclocked
In last case user can add new cpu example: core i3 8350k @ 5.0ghz, in same way time ago will be possible add new linux distribution
For memory values is more simply: this fields can be have this values, for example: 1GB - 2GB - 3GB - 4GB - 6GB - 8GB - 12GB - 16GB - 24GB and 32GB
In video card version can improve with user provide information, example: on nvidia propietary 387.12 - 387.34 - 390.12 and others, on mesa for example 17.1 - 17.2 - 17.3 and others
Videocard vendor and driver type is really good addition now
Thanks
https://bugs.winehq.org/show_bug.cgi?id=44351
--- Comment #4 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to mrdeathjr28 from comment #3)
Hi another interesting idea
The rule in bugzilla is one issue per bug report. Other ideas don't belong in this report.
https://bugs.winehq.org/show_bug.cgi?id=44351
--- Comment #5 from as3mbus asembus@gmail.com --- (In reply to Rosanne DiMesio from comment #2)
The idea is to have a way to save an unfinished version of a test report and be able to come back later and finish it.
exactly, it's just a feature request for better appdb experience. for me a week would be enough to save the draft but, maybe a month or a year for busy people. i believe testing an app wont take much time, and by leaving it for too long you'll forgot everything you tested.
-
wine-bugs＠winehq.org