Monaco (M7) Tests Part II

Status:

Complete = DONE

Failed =

In Progress =

For Bugs found in a Test, document them in the status using the BGQ command, for example Bug 1

Manual Tests

Core

Test Status Tester
Virtual-directory browser DONE P8 Team (Dave)
RESTdoc tables (web UI) Not a test for sMash ( Bug 5046 ) P8 Team (Dave)
RESTdoc tables (with CLI) Not a test for sMash ( Bug 5046 ) P8 Team (Dave)
JavaDoc completion Only a cursory look for main classes/ information P8 Team (Colin)
CLI Verification DONE P8 Team (Dave)
Groovy Error Handling DONE P8 Team (Dave)

Data

Test Status Tester
Zero Data DONE P8 Team (robinf)
Zero Resource Model DONE (with Derby & MySQL) P8 Team (robinf)

Security

Test Status Tester
User Service Application DONE P8 Team (Andy)
File Based User Service Command (Command Line Interface) DONE P8 Team (Andy)
XOREncoder Command (Command Line Interface) DONE P8 Team (Andy)
OpenID support DONE P8 Team (Andy)

CLI tests

Test Status Tester
Confirm CLI reference doc and CLI help match DONE Bug 5033 China Team
Confirm Repository Replication Instructions DONE China Team

Installer tests

Test Status Tester
Verify install and create for Windows China Team
Verify install and create for Linux DONE China Team (zhuke)
Repeat for console mode DONE China Team (zhuke)
Test CD version without network connectivity (local only) DONE (Bug 5091 - fixed) (Bug 5008 - fixed) Bug 5031 China Team (zhuke)
Test CD version without network connectivity (remote later) (this instruction is as same as previous section, need update?) China Team (zhuke)
Test CD version of RTE installer Bug 5119 Bug 5121 China Team (zhuke)

P8

Test Status Tester
End to end test Bug 5057 The out of date Developerworks article has been fixed but this test seems to be a test of the Eclipse tooling and so would seem invalid for GA content Hursley Assemble Team (Dave)
Install and run phpBB Bug 5060 - blocked by out of date blog entry Hursley Assemble Team (Dave)
Install and run SugarCRM   Hursley Assemble Team (Dave)

Assemble Connection

Test Status Tester
Send email DONE Core Team (Greg)
HTTP tests DONE Core Team (Greg)
REST2SOAP test DONE Core Team (Greg)

Assemble Flow

Test Status Tester
Start the samples project DONE Core Team (Tony)
Run the flows in the sample project DONEBug 5049 Core Team (Tony)
Launch and run the sample flows in assemble tooling DONE Core Team (Tony)

Assemble Messaging

Test Status Tester
Store and forward round trip tests DONE Core Team (Mandar)
Broker stats tests DONE Core Team (Mandar)
Dynamic pipe config test DONE Core Team (Mandar)
External client OSGI test DONE Core Team (Todd)
Messaging sample test DONE Core Team (Mandar)

Eclipse Tooling

Test Status Tester
Eclipse-Java/Groovy
-Use Update Manager to get Project Zero plug-ins
-Create a new application and run it
-Export/Import Project Zero application
-Standalone Export of Zero Application
-Repository Management/Resolver
-Groovy Debug/Global Context Debug view
-Code completion
DONE Core Team (Chandran)
Eclipse-PHP
- Use Update Manager to get Project Zero PHP plug-ins
-Create a new PHP application and run it
-Debug a PHP application
DONE Core Team (Todd)

IDE

Test Status Tester
Installing and running the IDE Bug 5170 Bug 5199 Bug 5200 Bug 5206 Bug 5207 Core Team(Tom/mac; Greg/linux; Tony/windows))
IDE Application Manager Tests
o Create a new app
o Create Employee Demo
DONE windows (Bug 5174 Bug 5176)
Bug 5196 Bug 5195 Bug 5182 Bug 5184 Bug 5186 Bug 5187 Bug 5205 Bug 5209 Bug 5210
Core Team(Madhu/mac; Mandar/linux; Darryl/windows)
* IDE Application Tests
o File Editor tab - Code Editor
o File Editor tab - Visual Page Editor
o File Editor tab - Visual Flow Editor
o Running the application
o Dependencies tab
o Explore tab
Bug 5157 Bug 5158 Bug 5160 Bug 5161 Bug 5168 Bug 5171 Bug 5173 Bug 5208 Core Team (Todd/mac; Madhu/linux; Tony/windows)
IDE Autobuild Tests
* Trash.Compile when Java file changes
* Resolve then compile when ivy.xml changes
* Resolve then compile when dependencies change
DONE Linux Bug 5201 DONE Windows Bug 5183 Bug 5179 Core Team (Tom/mac; Mandar/linux; Chandran/windows)

Samples

Test Status Tester
employee.demo on Eclipse Bug 5018 DONE Core Team (Chandran)
employee.demo on CLI DONE Core Team (Madhu)
books.demo on Eclipse (Atom sample) Bug 5021 DONE Core Team (Chandran)
books.demo on CLI DONE Core Team (Madhu)
employee.resource.demo on Eclipse DONE Core Team (Chandran)
employee.resource.demo using CLI DONE Core Team (Madhu)
Flickr Mashup DONE Core Team (Chandran)

Documentation

Source: http://aeneid.rtp.raleigh.ibm.com/sMash/1.0.x/docs/

Please mark pages as

Complete = DONE

or Failed =

Open defects for problem and note them in the table using the BGQ command, for example Bug 1

"Tester" owns that row and the following until the next Tester.

We're looking for glaring errors: copy/paste, missing images, broken links, outdated samples. The last one might take some digging, but we need to get it right. We also need to change all references to Project Zero as a product to WebSphere sMash. See the naming rules below:

Refer to the coding practices below:

Here's the overall link to the clean up, best coding practices, and "writer's boot camp" files:

http://www.projectzero.org/wiki/bin/view/Development/DevDocumentation

Specifically, they are:

Cleaning up files: http://www.projectzero.org/wiki/bin/view/Development/CleaningExistingFiles

Article development: http://www.projectzero.org/wiki/bin/view/Development/ArticleDevelopentStandards

Writer's boot camp: http://www.projectzero.org/wiki/bin/view/Development/WritersBootcamp

Naming Rules:

Documentation Reviewers, as you review the documentation for the sections for which you are assigned, be sure to pay close attention to any usage of the product name and make changes according to the guidance that follows. You should not make blanket changes from Zero to sMash, since zero can still be used in package names, module names and path names.

Any instance of a product name in the documentation must follow the following guidance:

Product name should be:

Official Product Name:

  • "IBM WebSphere sMash" (first occurrence)

Product Short Name:

  • "WebSphere sMash" (any subsequent occurrence)

Official Product Name:

  • "IBM Reliable Transport Extension for WebSphere sMash" (first occurrence)

Product Short Name:

  • "IBM Reliable Transport Extension" (any subsequent occurrence)

NOTE: Look for and replace any product name usage which at present could include: "Project Zero" "Zero" (in some usages obviously this is valid e.g. Zero Resource Model) "RTE" "Reliable Transport Extension"

Reliable Transport Extension Guide

Section Status Tester
Reliable transport extension DONE Core Team (Madhu)
* Store-and-forward processing in multiple messaging broker topologies DONE Core Team (Darryl)
* Configuration for the reliable transport extension DONE Core Team (Darryl)
o Configuring a messaging broker DONE Core Team (Darryl)
o Configuring connections to messaging brokers DONE Core Team(Sandra)
o Securing messaging resources DONE Core Team (Sandra)
* Using messaging within Project Zero applications DONE Core Team (Sandra)
o Using messaging with the Connection API DONE Core Team (Mandar)
o Messaging kicker and receiver DONE Core Team (Mandar)
o Using messaging within flows DONE Core Team (Mandar)
o Messaging sample DONE Core Team (Greg)
* Broker statistics API DONE Core Team (Greg)
* External client for the reliable transport extension DONE Core Team (Todd)
o Sample class jdbc.wrapper.XAResourceInfoImpl DONE Core Team Todd)
o Sample class jdbc.wrapper.XADataSourceProxy DONE Core Team (Todd)
* Deployment notes and troubleshooting DONE Core Team (Todd)

Getting StartedGuide

Section Status Tester
Installing and configuring: Command Line Interface Bug 5056 DONE Core Team (Tony)
Using the Project Zero Application Builder Bug 5056 DONE Core Team (Tony)
Installing and configuring: Eclipse for Java and Groovy Bug 5056 DONE Core Team (Tony)
Installing and configuring: Eclipse for PHP Bug 5056 DONE Core Team (Tony)

Dev Guide

Section Status Tester
* Overview of Core guide DONE P8 Team (Dave)
o Project Zero concepts DONE P8 Team (Dave)
+ Global context DONE P8 Team (Dave)
+ Event processing DONE P8 Team (Dave)
+ Application directory layout DONE P8 Team (Dave)
+ Virtualized directories DONE P8 Team (Dave)
+ Security considerations DONE P8 Team (Andy)
# Authentication DONE P8 Team (Andy)
# OpenID authentication DONE P8 Team (Andy)
# Security tokens DONE P8 Team (Andy)
# User service DONE P8 Team (Andy)
* File-based user service DONE minor update to doc Chandran
* LDAP user service DONE Chandran
o Writing Java™ handlers DONE Chandran
o Writing Groovy handlers DONE Chandran
o Writing PHP Handlers DONE Chandran
o Accessing global context DONE Chandran
o Configuration DONE Chandran
o Resource (REST) programming model and conventions DONE Todd
o JSON support DONE Todd
o File serving DONE Todd
o Response rendering DONE Todd
o URIUtils DONE Todd
o Calling a remote resource DONE Chandran
+ Using the Connection API DONE  
+ Sending an e-mail using EmailConnection DONE  
+ Configuring destinations DONE  
+ Configuring protocols DONE  
+ Configuring connection handlers DONE  
o Firing events DONE Todd
o Extending Global context DONE Sandra
o Global context Commands DONE Sandra
o Validators and validation DONE Sandra
o Nested resources in Project Zero DONE Sandra
o HTTP error handling DONE Sandra
o Creating a connection handler DONE Tony
o Creating a custom protocol transport DONE Tony
o Protocol reference DONE Tony
+ HTTP and HTTPS protocols DONE Tony
+ SMTP protocol DONE Tony
+ File protocol DONE Tony
+ Event protocol DONE Tony
o Simple logging connection handlers DONE Tony
o Extending security DONE Chandran
o Extending token support DONE Chandran
o Leveraging Trust Association Interceptors (TAIs) DONE Chandran
o Extending user service DONE Chandran
o Leveraging XOREncoding DONE Chandran
o Zero XML Encoder Utility DONE Chandran
o HTTP configuration DONE Sandra
o SSL configuration DONE Sandra
o JVM configuration DONE Sandra
o Proxy configuration DONE Sandra
* Command line interface tasks DONE Core Team (Madhu)
o Dependency Management DONE Core Team (Todd)
o Module Classpath DONE Bug 5056 (minor) Core Team (Tony)
o Module Tasks reference DONE Core Team (Todd)
o Module Group tasks reference DONE Bug 5055 Core Team (Darryl)
o Repository Tasks reference DONE Core Team (Sandra)
o Creating a new CLI task DONE Core Team (Chandran)
* Configuring data access DONE P8 Team (robinf)
o Database Setup Tool DONE P8 Team (robinf)
o Common query patterns DONE P8 Team (robinf)
o Advanced query patterns DONE P8 Team (robinf)
o Updating the database DONE P8 Team (robinf)
o Database transaction patterns DONE P8 Team (robinf)
o Extending data access DONE P8 Team (robinf)
o Configuration and vendor differences DONE P8 Team (robinf)
o PHP data access DONE P8 Team (Steve)
o Troubleshooting zero.data DONE P8 Team (robinf)
* Zero Resource Model Overview DONE Madhu
o Zero Resource Model Quick Start Tutorial DONE Mandar
o ZRM CLI Tasks DONE Mandar
o Configuring the Resource Model DONE Mandar
o Resource model declaration DONE Madhu
o Programmatic Model API DONE Madhu
o Resource Model HTTP REST API DONE Greg
o Using Dojo with the Zero Resource Model DONE Greg
o Tuning the Resource Model DONE Greg
* REST API documentation (zero.restdoc)   Madhu
* Client programming with Dojo DONE Todd
* Active content filtering (ACF) overview DONE Tony
o Active content filtering DONE Tony
o Active Content Filtering: Default HTML filters DONE Tony
o Active Content Filtering: Custom HTML filters DONE Tony
o Protection against Cross-Site Request Forgery (CSRF) attacks DONE Tony
* Atom support DONE Todd
* Runtime management DONE Sandra
o Zero Management Tasks reference DONE Sandra
o Zero socket opener DONE Sandra
o Deployment Recommendations DONE Chandran
* Using RSS Support DONE Chandran
* Using the Assemble component Using a flow DONE Core Team (Madhu)
o Getting started with Assemble flow DONE (Madhu)
+ Creating a simple feed flow DONE  
+ Creating a simple Assemble flow DONE  
+ Creating a simple extension activity DONE  
+ Troubleshooting zero.assemble.flow DONE  
o Using flows DONE Bug 5077 (Darryl)
+ A Flow language example   DONE Bug 5077  
+ Creating and running a new flow DONE Bug 5077  
+ Flow instance cleanup DONE Bug 5063  
o Flow activities DONE (Todd)
+ Writing extensions in flow DONE (Todd)
+ Writing Extensions in Groovy DONE (Todd)
+ Activity Validation DONE (Todd)
+ REST Service Invocation in Assemble Flow DONE (Todd)
+ Simple collaboration in Assemble Flow DONE (Todd)
o Flow programmatic API DONE (Greg)
o Flow language reference DONE (Sandra)
+ Flow language behavior and syntax DONE  
+ Running processes and activities DONE  
+ Built-in activities reference DONE  
+ Extension activities reference DONE  
+ Feed operators reference DONE  
+ XML operators reference DONE  
* Assemble flow management DONE (Darryl)
* Assemble Web-based visual tooling DONE (Tony)
o Configuring the graphical tool DONE  
o Using the GUI to work with flows DONE  
o Using the GUI tool to manipulate a feed DONE  
o Adding a custom activity to the tooling DONE  
o Advanced features DONE (Todd)
* REST to SOAP extension DONE (Todd)
* Protocol extension for JMS DONE (Todd)
o Connection protocol reference DONE (Todd)
o Configuring connections to the external provider DONE (Todd)
o Working with javax.jms.Message objects DONE (Todd)
o An example scenario using the protocol extension for JMS DONE (Todd)
* Timer service DONE (Greg)
* Kicker DONE