I went through it again and it reads much better to me. I like the
additional explanations given and the intro at the top of the page.
Provision, then execution. The notes and boxes distributed throughout
are also useful. Some remaining concerns:
-- 'Viewing subunit files' section is a bit buried now, can this be
worked into the top of the execution section?
-- Can the execution section be separated more clearly? The note is good
and useful information, but there's one sentence under 'executing tests'
and it simply says 'The touch testing repository supports both autopilot
and UTAH test definitions'. A little narrative here would help.
In addition, ever the pioneer, Nekelesh is using this document to try
and fix the clock app issues on the dashboard. I've asked him to report
back so I'll share his feedback with you once I get it.
Thanks,
Nicholas
On 03/12/2015 11:17 PM, Francis Ginther wrote:
Nicholas,
I've updated the document again and tried to give more emphasis to
some examples. If you have time to take another look, please let us
know if this update helps.
http://ubuntu-test-cases-touch.readthedocs.org/en/latest/
Also, I'll pursue some updates to the wiki undre
https://wiki.ubuntu.com/CI.
Thanks,
Francis
On Mon, Mar 9, 2015 at 4:02 PM, Nicholas Skaggs
<[email protected] <mailto:[email protected]>>
wrote:
On 03/04/2015 09:43 AM, Nicholas Skaggs wrote:
On 03/03/2015 05:28 PM, Francis Ginther wrote:
Also, as suggested we should link this information from
developer.u.c to make it available to a wider audience, in
addition to announcing it publicly on the mailing
list. Finally, I
can help make sure the core app developers themselves
directly
receive this information.
We can provide the content if you can give a
recommendation on where it should live. I poked around and
found [3] as a possible candidate. These CI testing tools
only apply to the core-apps and internal apps, so pointing
developers working on some other app toward this makes no
sense.
I haven't thought much about it; I'll bring it up with my
team. Off the top of my head, something off of
https://developer.ubuntu.com/en/apps/quality/
Nicholas
Francis,
After chatting with dpm, it seems like a link on
developer.ubuntu.com <http://developer.ubuntu.com> doesn't make
sense. The information is quite specialized, and is probably OK on
the wiki and readthedocs. So let's scrap that idea.
That said, we have a concern that the story of 'how to recreate
the dashboard results', is still not well covered. As this use
case was the drivingmotivation for wanting the documentation, it
makes sense to specifically cover it. An actual example or
walkthrough of recreating a test from the dashboard would be
helpful imho.
Nicholas
--
Francis Ginther
Canonical - Ubuntu Engineering - Continuous Integration Team
--
Mailing list: https://launchpad.net/~canonical-ci-engineering
Post to : [email protected]
Unsubscribe : https://launchpad.net/~canonical-ci-engineering
More help : https://help.launchpad.net/ListHelp
