lubuntu-qa team mailing list archive

[Nicholas Skaggs <nicholas.skaggs@xxxxxxxxxxxxx>]

Sure Phil.

Chad, it sounds like your already on the right track with the autopkg 
test. If you wish to add in autopilot testing, we could help out with 
that as well as a quality community. However;

autopilot launch -i Gtk chromium-browser
Gtk-Message: Failed to load module "autopilot"

That means we can't introspect it using autopilot so testing is limited 
/ if at all possible. I know the upstream chromium team has a test 
suite, and again, getting it passing using autopkg tests is probably the 
best first step.

Nicholas

On 07/19/2013 05:58 PM, Phill Whiteside wrote:
> Hi Nicholas,
>
> I do believe that Chads request falls squarely in the automated test 
> department.... Is there some kind soul who will set up the test case 
> for Chad? (Begs). This is really a case of an urgent automated test 
> case to check the incoming releases, as they can be security releases 
> as well.
>
> Regards,
>
> Phill.
>
> On 19 July 2013 18:45, Chad Miller <chad.miller@xxxxxxxxxxxxx 
> <mailto:chad.miller@xxxxxxxxxxxxx>> wrote:
>
>     On Fri, Jul 19, 2013 at 12:15 AM, Phill Whiteside
>     <PhillW@xxxxxxxxxx <mailto:PhillW@xxxxxxxxxx>> wrote:
>
>         Hi,
>
>         just noticed on a recent bug report. I'd like to share my
>         reply to it which I sent to social media (Well, PRISM has
>         caused some ructions).
>
>             And this an announcement, not an invite to another flame
>             war... I've spent a lot of time trying to encourage
>             chromum (not chrome) to be updated for those who choose to
>             use it. One of the major tasks was for the security
>             updates to be released regularly [done] and for the qa
>             people to have access to the stable daily builds so we can
>             test them before they get released. After a lot of work,
>             and many months of discussions, chromium stable release is
>             now available from a 'standard' (approved) area. So, in
>             answer to those who thought myself, chad and Alex Shkop
>             were sitting around doing nothing....
>             https://launchpad.net/~chromium-daily/+archive/ppa
>             <https://launchpad.net/%7Echromium-daily/+archive/ppa>
>
>             and here's the active one....
>             https://launchpad.net/~chromium-daily/+archive/stable
>             <https://launchpad.net/%7Echromium-daily/+archive/stable>
>
>             If you like testing, use the new ppa :)
>             As a foot note, I'd like to thank Alex for all the work he
>             has done and also thank Chad for his un stinting work on
>             getting chromium back up and running.
>
>
>
>     Hi all.  I'm happy to keep chromium building and testable in a
>     public place, but upstream releases come about every week, and
>     between patch integration, ARMHF architecture build failures,
>     ARMHF build time, and #security review and re-build, often the
>     next release has arrived.  People are already screaming for
>     updates days before QA could even begin to test.  I value
>     assurance of quality, but I can't wait for long on human testing.
>
>     One thing I would like QA help with is automated tests.  I've
>     started some autopkgtest smoketest and build-time unit testing,
>     but I'd like to have automated
>
>     - simple performance test
>     - UI translation test for languages that will be patched in from
>     Launchpad soon (?!)
>     - integration test with webapps patches and extension
>     - learning what tests I didn't know to add to this list
>
>     I would love some patches or guidance.
>
>     lp:~chromium-team/chromium-browser/saucy-working
>
>     http://www.chromium.org/developers/testing/browser-tests
>
>     - chad
>
>
>
>
> --
> https://wiki.ubuntu.com/phillw