We have moved to a new Sailfish OS Forum. Please start new discussions there.
26

Integrate QA testing scripts with Sailfish SDK [released]

asked 2013-12-25 20:05:49 +0200

Elleo gravatar image

updated 2013-12-25 20:08:20 +0200

pnuu gravatar image

It'd be great if the QA scripts used to check the validity of packages could be included in the SDK and run automatically as part of the QtCreator packaging process. That way we can be alerted to aspects of our packages that need fixing prior to submitting them to the Harbour.

Thanks!

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by kaltsi
close date 2014-08-22 16:50:17.380987

4 Answers

Sort by » oldest newest most voted
8

answered 2014-01-02 14:39:12 +0200

Kontio gravatar image

updated 2014-01-15 17:24:48 +0200

This is (as many other things too) work in progress. It's more likely that first the script will be ran already during the upload to harbour, so you see the output already then, than it will be available in SDK. Also the script it self is not yet in a state that it can be released. Too many changes, false positives etc.

EDIT - 15. Jan 2014
Seems I can't see the future either :-) it will first be made available as part of the SDK Control Center, it turned out to be the fasted possible way:
https://lists.sailfishos.org/pipermail/devel/2014-January/002924.html

edit flag offensive delete publish link more

Comments

Cool, ability to run automated QA while uploading to Harbour is good enough - please add also some kind of waive option (if developer thinks it's ok, it can go to manual check). But even basic check is better than nothing to save developers and QA resources. Now after five days, let's fix the issue!

Rezza ( 2014-01-03 13:36:48 +0200 )edit

Excellent, great to see this becoming part of the SDK; makes life much easier :).

Elleo ( 2014-01-16 16:39:22 +0200 )edit
2

answered 2014-01-02 14:30:15 +0200

Khertan gravatar image

updated 2014-01-02 14:31:34 +0200

@Artem > "cheking procedure is closed, so you cannot just easily find a hole in the automated rules"

Security by obscurity ... yeah we all know what this means :)

edit flag offensive delete publish link more
1

answered 2013-12-27 00:32:56 +0200

Artem gravatar image

Apple App Store does it quite conveniently so that your app is uploaded to server right from XCode, automated checks are run there and only if they pass fine, you are allowed to actually submit.

This way: 1. devs are guaranteed to pass basic checks before they upload 2. checks are always up to date 3. cheking procedure is closed, so you cannot just easily find a hole in the automated rules

edit flag offensive delete publish link more
1

answered 2014-04-15 13:39:44 +0200

jake9xx gravatar image

Stating the obvious here but RPM validator has been available in the SDK for a quite some time. Just open the SDK Control Center and look for 'Harbour Tools' column. It has section for RPM validator and it performs the steps Store QA does for applications.

edit flag offensive delete publish link more

Comments

Or you can read the accepted answer and see that this is already stated there.

Mohjive ( 2014-04-15 14:52:34 +0200 )edit

Question tools

Follow
8 followers

Stats

Asked: 2013-12-25 20:05:49 +0200

Seen: 724 times

Last updated: Apr 15 '14