Re: [ ANNOUNCE ] KISStester
 

Nope, seems that widget has not been ported.

However.

We could drop the label part from the checkbox item and jut put a QLabel beside it, and the QLabel in turn can contain rich text which we CAN style like that.

In other news, it seems it DOES have a tristate mode, but my quick test showed no difference in operation (might be me, or a Qt bug, or some Hildon recommendation).

Re: [ ANNOUNCE ] KISStester
 

When I run kisstester it opens the login dialog. I enter my credentials and then the program exists. Log on console:


run-standalone.sh python /opt/kisstester/kisstester
KISStester
Linux-2.6.28-omap1-armv7l-with-debian-testing-unstable
WARNING:root:Logging in
{'username': '', 'midcom_services_auth_frontend_form_submit': 'Login', 'password': ''}
HTTP Error 403: Forbidden
Traceback (most recent call last):
File "/opt/kisstester/kisstester", line 17, in <module>
kisstester_main.start()
File "/opt/kisstester/kisstester_main.py", line 270, in start
mainw = MainWindow()
File "/opt/kisstester/kisstester_main.py", line 89, in __init__
self.showRecent(True)
File "/opt/kisstester/kisstester_main.py", line 254, in showRecent
self.login()
File "/opt/kisstester/kisstester_main.py", line 117, in login
if not self.settings.show():
File "/opt/kisstester/settings.py", line 29, in show
if self.exec_() and self.accepted():
TypeError: native Qt signal is not callable

Why does it say "WARNING:root:Logging in"? I did not run it as root.

Re: [ ANNOUNCE ] KISStester
 

Whoa, interesting error... Can you tell which PR (settings->about) and PyQt (dpkg -l | grep python2.5-qt4) do you have ?

PS. Don’t let the root thing fool you - python calls the default logger ’root’, hence the message (it’s not about the username).

Re: [ ANNOUNCE ] KISStester
 

ii python2.5-qt4-common 4.7.4-maemo0 Shared files for PyQt4
ii python2.5-qt4-core 4.7.4-maemo0 Python bindings for Qt4 Core components.
ii python2.5-qt4-gui 4.7.4-maemo0 Python bindings for Qt4 Core components.


PR version 10.2010.19-1

Re: [ ANNOUNCE ] KISStester
 

Now I tried kisstester under scratchbox, x86 target. I get the exact same error message (having the same package version for qt4. python-qt4 and kisstester (0.3-maemo2).

Re: [ ANNOUNCE ] KISStester
 

It s a pyqt bugs : https://bugs.launchpad.net/qbzr/+bug/394125

This is due to new signal.

use : if QDialog.exec_(self)==QDialog.Accepted:

Re: [ ANNOUNCE ] KISStester
 

Another bug, dunno how easy it is to fix, the progress dialogues are system- rather than application-modal. This means you can't switch to another app whilst it's "Loading extras-devel data", for example.

Re: [ ANNOUNCE ] KISStester
 

Thanks, pushed to gitorious.

Qt has a few of these attributes, so I guess it’s doable, just needs a little playing with.

Re: [ ANNOUNCE ] KISStester
 

New version available, biggest change is that the load/login operations are done asynchronously -> should not block, plus a few smaller fixes. What do you think is perhaps missing and needs to be done before I take it to extras-testing (apart from displaying existing comments, which is already in the queue) ?

Re: [ ANNOUNCE ] KISStester
 

The new version seems to fix that logging on bug as reported by
gilead "When I run kisstester it opens the login dialog. I enter my credentials and then the program exists".

I had the exact same problem, but am now able to logon trough KISStester, thanks!

Re: [ ANNOUNCE ] KISStester
 

It would be helpful if there was a button "show contents" near the "[x] Optified" check button that will show the output of "dpkg -L <packagename>" in a new stacked window. This way, it's easy for the tester to verify the optified-ness (could be that this was already suggested, didn't take the time to read the whole thread - sorry about that :).

Re: [ ANNOUNCE ] KISStester
 

There was the hope that some people will step up and provide patches... but that has not happened yet. Showing dpkg -L is easy, though not necessarily helpful (as for eample you don't see which seemingly unoptified paths are actually symlinked).

Re: [ ANNOUNCE ] KISStester
 

Feature request:
In the menu bar, 2 buttons -

1. "Legend" - displays a screen with the symbol & what it represents, also explains why some entries are dark and some light

2. "Testing Procedure" - A button which links to the extras-testing wiki page at
http://wiki.maemo.org/Extras-testing

Re: [ ANNOUNCE ] KISStester
 

1. tried logging in with tmo login details and the app got stuck at the connecting part, no top right corner X button available, had to kill the process the following morning

2. again stuck, this time at "loading extras-testing data" part, and cancel does not do anything. cannot seem to close the program without killing the process again.

Re: [ ANNOUNCE ] KISStester
 

woha, thought it was some app which will tell you how bad or a good kisser are you (place your mouth here.... testing......... you are a sloppy kisser) lol.
since the app is intended to streamline the process of voting apps that is targeted towards general users, the app name might mean something else than what it does (almost all maemo apps have names not identifying what it does)
can you change the app name to something descriptive.
Maemo App Catalogue Promoting? perhaps? or any others ?

Re: [ ANNOUNCE ] KISStester
 

I also had the same problem with getting stuck at "loading extras-testing data" when I tried kisstester yesterday (the app did not react when pressing Cancel).

Re: [ ANNOUNCE ] KISStester
 

There is a major rewrite underway (well, it's almost-complete and up on gitorious), I just haven't unleashed it to extras-devel yet. This one uses proper async Qt functions for the various network stuff (in plain English - it doesn't block, you you can cancel :) ).

As for the name... well... Dunno, never was good at naming :)

Re: [ ANNOUNCE ] KISStester
 

Just wanted to check what is the status with the new kisstester update; when can the updated version be expected? :)

Re: [ ANNOUNCE ] KISStester
 

This programme is such a good idea - standardise testing procedures. Is anyone maintaining it?

The UI kind of dies when it launches. If the software's busy, there's no indication of what it's up to. After a min or two it settles down.

Going to go through the questions...
Has proper bug tracker - can this be assessed automatically by running wget (or similar) over the package page?
Contains proper licence - where should the tester look for the licence? Package page, UI title bar... ? If the licence is in a standard place, again - could a script look for it?
No dubious content - Should this not be "No dubious content without clear indication" - surely naughty things can exist so long as the sensitve are aware? Or would such things infringe on nokia's willingness to host the item in the repos?
No broken functionality - OK, this is potentially massive and covers everything from doesn't work at all to small items not working in the way one thought they might. Perhaps breaking it down on a second page/tab a bit might help? This would give an opportunity to check for UI functionality and documentation.
Optified - is this testable automatically? Other than not wiping out one's rootfs, how does one actually "know" a package has been properly optified?
Resource usage - assuming the package doesn't max out cpu all the time, what's "reasonable". Some tasks are just intensive e.g. converting videos. Perhaps this could be automatically tested by checking what else can be done while the programme is being run?
Power use - again, so long as the programme doesn't short the device, what is reasonable?

For the login, it needs to be able to do so with bugs.maemo as well as maemo.org to write on the package page.

I don't know how/why but KISStester launches Opera for the web interactions. Probably these buttons just need redefining? Some buttons don't work.

I've suggested automating a few of the above tasks, which might seem a bit pointless because once one person has performed the test, surely it'll be the same for all users? Not on the N900! Everyone has a different device set up so the results of performance and storage tests would be different for every device. also, if everyone runs a standard test for licence and bugtracker location etc. , the developer(s) will be sure it's correct (or not!).

KISStester would work really well if it could be used with a Wiki page to flesh out the checklist. Also, am I missing something - is there a way to test -devel packages with it? On the same note, might be useful to be able to paste a comment from KISStester to the maemo.org downloads section for those packages that have made it to extras.

Maybe once tidied up, add to CSSU testing so more people provide useful comments and/or promote/fail packages?