canonical-ci-engineering team mailing list archive

[Thomi Richards <thomi.richards@xxxxxxxxxxxxx>]

Hello,


It's highly likely that goal for the inaugural sprint for the QA projects
team will revolve around getting a number of test cases 'up to scratch' to
be handed over to the CI team.

The problem is that the CI team haven't had time to complete the 'test
handover checklist' we discussed in D.C. (as an aside, I'd love to know
from the scrum-experts on this list whether there's a standard way to
manage dependencies between multiple scrum teams). Additionally, the
'handover' doesn't seem like something that fits within the scrum
framework. I'd like some direction from the CI team as to how you see this
happening.


Regarding the tests themselves, I'd love to get a rough idea of what your
requirements are. I have jotted down some thoughts that might help get us
started:


   - All test suites in dep8/autopkgtest format.
      - Results to be stored in a subunit binary stream.
      - ...which is an archived artifact.
   - Tests to be in a launchpad branch (of a specific project? any project?)
   - Evan mentioned that he didn't want to keep running tests in jenkins.
   The tests we'd like to hand over currently run in jenkins. What's the
   proposed alternative? How can we set up those test jobs to prove that these
   suites are stable?


I'd love some guidance on the points above, so the work we produce is
aligned with what CI will accept.

Please accept my apologies if this seems like me trying to interrupt your
sprint. I guess that 's exactly what I'm doing, but you should let me,
because... reasons :D

Cheers,
-- 
Thomi Richards
thomi.richards@xxxxxxxxxxxxx