Difference between revisions of "PTP/testing/7.x"

Revision as of 03:10, 14 May 2013

Test Plan for PTP 7.x Release

This plan describes the tests that will be undertaken to verify the 7.x series of PTP releases - Eclipse 7.0.0 will be available June 26, 2013 with the Eclipse Juno (4.3) Simultaneous release.

Test Setup

The following steps should be carried out prior to testing PTP. Refer to the release notes for the appropriate PTP version if necessary.

1. Make sure you have Java 1.6 or later
2. Start with a fresh Eclipse installation
3. Use a new workspace for testing (or remove old testing workspaces)
4. Download and install the package "Eclipse for Parallel Application Developers" package
   • from http://eclipse.org/downloads Select "Developer Builds" at the top to get pre-release downloads.
   • If desired, update from nightly build: http://download.eclipse.org/tools/ptp/builds/kepler/nightly/
5. (Optional, Remote only?) install PTP server components using instructions from the 7.0 release notes.
6. Launch Eclipse on the test machine.
7. If you require an MPI program for testing, use the following code:

#include <stdio.h>

#include <mpi.h> 
int main(int argc, char *argv[]) 
{ 
  int i, rank; 
  MPI_Init(&argc, &argv); 
  MPI_Comm_rank(MPI_COMM_WORLD, &rank); 

  for (i = 0; i < 10; i++) 
  { 
     printf("hello from %d loop %d\n", rank, i); 
     sleep(1); 
  } 

  MPI_Finalize(); 
  return 0; 
}

Test Iterations

The following dates show the final build dates for the RC builds (+5 day). Eclipse platform is built on +0 day (a Friday). PTP is +3 which means that its build is completed on the +3 day (following Wednesday). Testing can begin using the Kepler aggregation site (http://download.eclipse.org/releases/staging) on +4 day (watch email) and later. The EPP build (e.g. Parallel Package) is generally available at the end of the +5 day (Friday), but official EPP testing can begin on the EPP day (+4) once the packages have been announced.

Testing on RC4, even though it is the "final" build, is still useful as any bugs can still be fixed in future bug fix releases of PTP, or Eclipse Kepler service releases (SR1, SR2). However, these fixes will not be included in the initial Kepler release (June 26).

• M7 May 10
• RC1 May 24
• RC2 May 31
• RC3 June 7
• RC4 June 14
• Release date for Kepler - June 26

Testers

Please add your name to this list, or remove the comment if you are participating in 7.0 - add a general comment to your general field of expertise/intended testing here 

• Greg Watson (remove this if participating in 7.0) - General, debugger
• Beth Tibbitts - General, PLDT, Feedback, Help, Install
• Dave Wootton (remove this if participating in 7.0) - IBM PE/LL, ...
• Wyatt Spear (remove this if participating in 7.0) - ETFw, TAU
• Jeff Overbey (remove this if participating in 7.0) - Photran, ...
• Jay Alameda (remove this if participating in 7.0)
• Galen Arnold (remove this if participating in 7.0) 
• Rui Liu (remove this if participating in 7.0) - Feedback
• Chris Navarro (remove this if participating in 7.0)
• Roland Schulz (remove this if participating in 7.0)
• John Eblen (remove this if participating in 7.0) - Sync
• Brian Watt (remove this if participating in 7.0) - ETFw
• Hari Krishnan (remove this if participating in 7.0)
• Brandon Gibson (remove this if participating in 7.0) - GIG,GEM
• Zhi Ming Wang - IBM Platform MPI

Test Matrix

The following test matrix shows who will be testing each component on the different supported architectures. Note that because PTP is client/server, you should list both the client and server architectures for each component being tested. For example, if you are testing PE on a Mac OS X x86 client and an AIX backend, you should list both these architectures.

When you find bugs, please open a bug report against the relevant component.

PTP 6.0 Testing page
?? Name was here for 6.0 testing, not updated for 7.0
* Only the GTK 2 version of Eclipse will be tested
*** AIX testing is for the server side only.
α Limited testing only
(client) indicates that eclipse runs here
(server) indicates remote target runs here
(R) will test remote usage
(L) will test local usage
## old (not updated to PTP 7.0 testing) - remove ## if you update this and/or confirm you are still testing this

Test Outlines

Initial overview of some features to be tested:

• Install & Update: install parallel package, try update scenarios from & to different RCs/releases, make sure feature names, versions, providers, ids, etc are correctly set in installation information for each of the features (Beth)

• Help: bring up help, make sure the pieces are all there, make sure topics are up to date, any version numbers referenced are correct, make sure links work between help docs (Beth)