linaro-release team mailing list archive

[Paul Larson <paul.larson@xxxxxxxxxxxxx>]

Depends... what kind of testing are you proposing to do?  Are you
wanting to just run the unit tests?  Where lava would probably best come
into play, is if you want to build an image from it, and try actually
booting the image.  I'm not sure how much problem we've had with that in
the past though.  Most of the bugs I've seen have been with things like
hwpack-create (which this wouldn't catch) or failing when building the
image with various options.

-- 
You received this bug notification because you are a member of linaro-
infrastructure-drivers, which is the registrant for Linaro Image Tools.
https://bugs.launchpad.net/bugs/888555

Title:
  Set up l-i-t testing on multiple archs and releases

Status in Linaro Image Tools:
  New

Bug description:
  We need to test l-i-t on all supported releases and architectures. We
  have seen a number of cases where new features are later found to not
  work on old releases or older versions of Python. We just had a
  problem with linaro-hwpack create not working on Oneiric 64 bit, but
  happily work on 32 bit.

  For testing new code and especially for release testing we would need
  to set something up to enable this since a single developer won't have
  access to all variants of installations.

  We could perhaps automate something to set up virtual machines on
  local dev PC:s with possible impact on TDD since tests would take many
  times longer to run. Perhaps we can use LAVA?

  For full coverage we'd need to test on all possible combinations of
  the below components (please add to them as you see fit), but that is
  probably overkill.

  Python:
      2.6
      2.7

  Ubuntu:
      Precise
      Oneiric
      Natty
      Maverick
      (how far back do we want to ensure support?)

  Archs:
      i386
      x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-image-tools/+bug/888555/+subscriptions