Test Plan for UIMA Version 2.3.0

This page documents the planned testing for the 2.3.0 release.
A lot of testing is already done by virtue of the Unit Tests done while creating the release. This page is for system/overall tests and reviews.

Test Schedule

Date(s)

Task

Nov 13

Start test phase

Nov 23 Dec ??

End of test, start release vote

Documentation Review

Summary

Assignee

Status

Resolution

Check Jira issues for necessary documentation updates.

All

 

 

Review UIMA-AS doc

Cwiklik/Epstein

done

some updates done - see Jiras

Review Sandbox docs

Sandbox project owners

 

 

License Reviews

Summary

Assignee

Status

Resolution

Review licenses

Schor, Goetz

Schor fixed up Sandbox lic., added top level uima-as ones RC7

done

UIMA framework tests

We invite everyone to help in testing the 2.3.0 release candidates, by downloading & installing it, and using it in your projects. Then report your success and/or failures. Please record the successes here, in this table:

Component

Description

Tester

Platform      

Which release candidate?

Status / Comments

install

install bin, run doc analyzer, run add src

Marshall

Windows
linux

RC-2, rc7 (Windows)

Windows - 100% for base and uima-as

install

install bin, run doc analyzer, run add src

Tommaso

Mac

RC-2

Mac - 100% for base

Eclipse

use eclipse update site to install plugins

Marshall

Windows

RC-2, RC7

Ok on Eclipse 3.5, both CDE and deploy editor 100%

source

built core and sandbox from source distribution

Thilo

Win

RC5

Ok with minor hickup, see UIMA-1694 (fixed in rc7)

Eclipse tooling

installed eclipse tooling from update site,
created project, tested pear installer and CVD

Thilo

Win

RC5

Ok with minor issue, see UIMA-1693 (was due to no UIMA_HOME env var)

Sandbox

Sandbox annotator spot test: whitespace
tokenizer, tagger, regex

Thilo

Win

RC5

Ok, previous issue with regex pear resolved

Comparing Source Distributions to svn exports of the tag:

uimaj - (RC7) diffs: using $ diff -b -r uimaj-2.3.0-07 ../rc7/uimaj-orig/uimaj-2.3.0-incubating/

Expected diffs:

  • Some files copied to top level, not in SVN. Eg. packageAllJavaScourcesIntoJar.bat etc.
  • A bunch of empty dirs in SVN (e.g., src/main/resources, fop-versions/.../fonts) are omitted in the src zip by the assembly maven plugin
  • The PearPackagingMavenPlugin has its own set of files, not used in the distr packaging, because it was merged into the main uimaj build, and its docs were combined. However SVN still has the older approach - individual Lic/Not/Discl, and its own docbook. Leaving these in SVN because I think we'll be wanting to make the pear maven builder a separate project
  • 2 projects in SVN not in the release because they're not used in building from sources
    • uimaj-internal-tools
    • uimaj-jet-expander

uima-as - RC7 diffs:

  • Some files copied to top level, not in SVN. Eg. README, RELEASE_NOTES, addSourceToJars etc.
  • 2 empty dirs in SVN, not in src distr src/main/resources

sandbox - RC7 diffs:

  • The generated html/pdf docs for the sandbox projects are kept in the source- for use by the website (to display them), but since they're big and generated, they're not in the source distribution.
  • empty dirs in SVN, not in src distr e.g, src/main/resources, src/test, lib, etc.
  • there is in SVN a file NoticeFileResearchLog.txt not shipped - not needed to rebuild. This file is for maintainers, and documents research into crafting the proper Notice file.

The focus areas for testing include:

  • Installation from the binary distributions, on various platforms
  • Installing the Eclipse plugins from the temporary update site (on people.apache.org/
  • Running of the core (e.g. document analyzer, CPE GUI etc., on sample/examples or on your project)
  • Running of UIMA-AS in various deployments
  • Running of the Sandbox components

Misc Running

Burn:

  • Large aggregate uima-as, ran with older remote components, aggregate ran using auto-deployment (runRemoteAsyncAE) (RC3).
  • New error handling - timeouts reset when cas comes back (prevents CASes timing out if stuck behind preceeding long-running ones) works.

Eddie:

  • Tested uima/uima-as on very large complex system - verified whole system worked and timings were as expected.
  • Tested compatibility with C++ - run co-located C++ annotators, ran core UIMA with C++ annotators, using UIMA-AS to deploy C++ annotators. These are just basic tests...

Jerry:

  • Ran the uima-as "extended" JUnit tests (these test take a long time because they have loops looking for intermittent issues).
  • No labels