Skip to main content
Jump to: navigation, search

TPTP-PMC-20071114

Attendees

  • Present:
    • Paul Slauenwhite
    • Oliver Cole
    • Mikhail Voronin
    • Alex Nan
    • Joanna Kubasta
    • Alan Haggarty
  • Absent:
    • Harm Sluiman - conflict
    • Guru Nagarajan
    • Chris Elford - ill

Previous Week

4.5

  • I3 TP2 test status:
    • Monitor:
      • Done.
    • Test:
      • Done.
    • Platform:
      • Probekit test suites are outstanding and will be done by EOD.
      • The remaining test suites are executed and the test results will be checked into CVS by EOD.
    • Trace:
      • There are no test suites in the smoke test bucket for the Trace project. Guru will add test suites to the smoke test bucket for the Trace project.
      • The Trace project has not meet the entry criteria for TP2. Mikhail reports that some testing has been done. Guru will provide an update on what tests were ran for the Trace project in I3 TP2.
  • Oliver will discuss the leadership of the Trace Project with Guru/Chris/Intel.
  • M3 Drop:
    • Currently waiting for the BIRT +2 driver (still building) to rebuild a candidate driver.
    • Since BIRT is late and we do not know when the build with complete, we will drop the I3 candidate.
    • Joanna will coordinate with Joel to drop the I3 candidate today as our M3 deliverable.
  • I4:
    • Each project lead will schedule the I4 defects and enhancements in the weekly schedule.
    • Paul added a document to the TPTP committer documentation site with the test pass criteria.
      • Please review and provide feedback.
      • Each project lead will schedule the work required to meet the test pass criteria in the weekly schedule in preparation for the I4 TP. It is the responsibility of the project leads to determine the acceptable level of testing for the full and smoke test bucket.
    • Each project will automate the manual tests in their project automated in preparation for the Test Automation Initiative (target: November 28, 2007).
      • The target is to have 50% of the manual tests automated by the start of I4 TP.
      • This work needs to be scheduled in the weekly schedule.
  • Weekly Schedule:
    • Monitor:
      • Updated.
    • Test:
      • Updated.
    • Platform:
      • Not updated.
    • Trace:
      • Attempted to update with a WYSIWYG editor, which corrupted the schedule.
    • The weekly schedule is hard to manually edit.
      • Any suggestions?
    • Oliver and Paul will add the require I4 milestones.

TPTP Webinar

  • If you cannot attend the live Webinar, you can view the recording.

Test Automation Initiative Update

EMMA Update

  • All of the Test Project committers started testing with the EMMA-instrumented driver (see the instructions for details) for I3 TP1 but could not continue:
    • Kendric/Jerome: First time testing TPTP so reverted to the TPTP SDK to reduce confusion.
    • Duwayne: Automated tests (AGR/JUnit/JUnit Plug-in tests) hang when running with EMMA since the EMMA JAR is missing from the class path and the </code>emma.rt.control=false</code> system property is required for the session JVM. Paul is investigating.
    • Paul: Complete manual tests using the EMMA-instrumented driver.
  • Paul published a EMMA report based on the manual testing statistics.

EclipseWorld 2007

  • Joe and Scott Schneider presented a tutorial (Achieving Continuous Integration With Eclipse TPTP and Java), which was well attended and received. There were ~25 paid attendees, and nearly all of them worked through the hands-on portion successfully (implementing an ASF service that appends resources to an existing working set, creating a new one if necessary.)
  • The Probekit talk that Joe presented for Guru drew about 18 people, and was also very well received. They asked good questions, the demos all went well, and several people have contacted me asking for the probes used in the demos for their own use.
  • Joe attended Steve's Static Analysis talk, which was standing room only and was also well received.

EclipseCon 2008 Update

  • Currently, there are only two submission for the Test and Performance category:
  • The Test and Performance category covers topics related to test and performance tooling that leverage Eclipse. Test and Performance tooling is used throughout the software development and test life cycle, from early unit testing, profiling, and tuning to post-deployment monitoring, tracing, and log analysis. This category is focused on the implementation, extension, and use of test and performance tooling - both open source and commercial - targeting a broad spectrum of systems including embedded, stand-alone, distributed, and enterprise. There is particular interest in exploitation and user experience of the Test and Performance Tools Platform (TPTP) project. Presentation types include:
    • Tutorial: A two hour presentation, with coding and/or a hands on workshop.
    • Long Talk: A one hour presentation that goes into detail and/or demonstration on a topic.
    • Short Talk: A five to ten minute presentation that covers the highlights of a topic.
    • Posters: Posters are presented at the poster reception session.
    • Birds of a Feather (BoF): BoF meetings are informal one-and-a-half-hour gatherings of people who want to talk about a particular topic.
  • If you are interested in proposing a talk or tutorial, please:
  • Important dates include:
    • November 19, 2007: Submission deadline.
    • December 10, 2007: Tutorials, Long Talks, and Short Talks selected.
    • January 19, 2008: Submissions open for posters and BoFs.

Profiling Update

  • Makil to update the criteria for the ideal J2EE user (e.g. application server, database, etc.).
  • Intel agrees to go public with this initiative.

Jolt Awards

Inactive Committers

  • Reminder for project leads to send notes to inactive committers inquiring if they want to be removed as TPTP committers.
    • Template note:
   In preparation for starting the TPTP 4.5 release, we are attempting to update our project's committer list.  Our project log indicates that you have been inactive as a committer (e.g. no CVS commits) for one or more releases.  If you would like to be removed as a committer, please send a request to <project mailing list>.

Action items

  • Guru: Provide an update on what tests were ran for the Trace project in I3 TP2.
  • Guru: Add test suites to the smoke test bucket for the Trace project. See the TPTP Testing Strategy for more details.
  • Oliver: Discuss the leadership of the Trace Project with Guru/Chris/Intel.
  • Joanna: Coordinate with Joel to drop the I3 candidate today as our M3 deliverable.
  • Makil: Update the criteria for the ideal J2EE user (e.g. application server, database, etc.).
  • All: Schedule the work required to meet the test pass criteria in the weekly schedule in preparation for the I4 TP. It is the responsibility of the project leads to determine the acceptable level of testing for the full and smoke test bucket.
  • All: Schedule the work required to automate 50% of the manual tests for their projects by the start of I4 TP in the

weekly schedule.

Back to the top