Re: [cbi-dev] Update for Dec. 20

[Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>]

On Wed, Dec 21, 2011 at 12:26 PM, Andrew Ross <andrew.ross@xxxxxxxxxxx> wrote:

Also, I'd like to get everyone thinking about testing. What kinds of tests do we need to ensure we run & pass so that we can have high confidence in this build?

For the eclipse project, there's at least 2 sets of tests that it would make sense to run (there are more sets, but 2 to start with :-)

1) is the automated test suite.  The build produces 2 zips, see http://download.eclipse.org/eclipse/downloads/drops/S-3.8M4-201112091447/index.php#JUnitPlugin

This can be unzipped, copy the correct SDK zip, and run using:

./runtests -os linux -ws gtk -arch x86_64 [optionally specify test]

on build.eclipse.org you need a virtual X server, for example.

As a 3.8 build includes all of the test plugins, they can be installed from the p2 repo.

2) the comparator logs can be examined (we might actually have 3.8 releng tests for that, I'm not sure).  The easiest way is to run your repo through a mirror, against an existing baseline repo:

          <p2.mirror source="file:${p2.repo}" log="${buildDirectory}/${buildLabel}/mirrorLog.txt" ignoreErrors="true" >
            <destination compressed="true" name="${p2.repo.name}" location="file:${updateSite}/${buildLabel}" append="true" format="file:${p2.repo}" kind="metadata" />
            <destination compressed="true" name="${p2.repo.name}" location="file:${updateSite}/${buildLabel}" append="true" format="file:${buildDirectory}/formatRepo" kind="artifact"/>
            <comparator comparator="org.eclipse.equinox.p2.repository.tools.jar.comparator" comparatorLog="${buildDirectory}/${buildLabel}/comparatorlog.txt">
                <repository location="${repoBaseline}" />
            </comparator>
        </p2.mirror>


Later,
Paul

-- 
Paul Webster
Hi floor.  Make me a sammich! - GIR