Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Documentation: Galileo Sprint5"
(→Sprint Goals) |
(Adding Demo scopes) |
||
| Line 20: | Line 20: | ||
'''Demo scope''' (2009-05-20): | '''Demo scope''' (2009-05-20): | ||
| − | * Integrate Swordfish and Tools Update Sites into Galileo | + | * '''Integrate Swordfish and Tools Update Sites into Galileo''' |
** Run vanilla Eclipse M7, use Update installer to install Swordfish Tooling feature from Galileo Update Site | ** Run vanilla Eclipse M7, use Update installer to install Swordfish Tooling feature from Galileo Update Site | ||
** Create target platform definition and provision Swordfish runtime bundles from Galileo Update Site | ** Create target platform definition and provision Swordfish runtime bundles from Galileo Update Site | ||
| − | * Make PDE build use the new 3rd party projects (Carry forward) | + | * '''Make PDE build use the new 3rd party projects (Carry forward)''' |
| − | * Run integration tests with PDE build | + | * '''Run integration tests with PDE build''' |
** Checkout org.eclipse.swordfish.build (and whatever else is required) | ** Checkout org.eclipse.swordfish.build (and whatever else is required) | ||
** Start 3rd party bundle build | ** Start 3rd party bundle build | ||
| Line 31: | Line 31: | ||
** Show output of integration tests | ** Show output of integration tests | ||
| − | * Change ODE version to 2.0 Smila (Carry forward) | + | * '''Change ODE version to 2.0 Smila (Carry forward)''' |
** show execution of simple process in ODE | ** show execution of simple process in ODE | ||
| − | * Exemplary policy processing | + | * '''Exemplary policy processing''' |
** show documentation of sample policy assertion | ** show documentation of sample policy assertion | ||
** Explain implementation | ** Explain implementation | ||
| Line 42: | Line 42: | ||
'''Goal: Tooling''': WDSL-first driven development. | '''Goal: Tooling''': WDSL-first driven development. | ||
| + | * <b>Generate JAX-WS Service Provider from WSDL</b> | ||
| + | Demo:<br> | ||
| + | - Eclipse help<br> | ||
| + | - New Project wizard<br> | ||
| + | - Import wizard<br> | ||
| + | - Cheatsheet<br> | ||
| + | |||
| + | Expectation:<br> | ||
| + | - System tests are passed<br> | ||
| + | - WSDL File is available in the Eclipse Workspase or in the Filesystem<br> | ||
| + | - new JAX-WS Service Provider created <br> | ||
| + | |||
| + | * <b>Running BPEL Editor</b> | ||
| + | Demo:<br> | ||
| + | - Swordfish Wiki documentation (how to get it running with Swordfish tooling)<br> | ||
| + | - Installing BPEL Editor from the Update site<br> | ||
| + | - run BPEL Editor<br> | ||
| + | |||
| + | Expectation ''(may be will be corrected after first results with BI)'':<br> | ||
| + | - no QA here.<br> | ||
| + | - BPEL Editor is available for download from update site.<br> | ||
| + | - BPEL Editor installed into Eclipse.<br> | ||
| + | |||
| + | * <b>Registry tooling (SR) integration</b> | ||
| + | Demo:<br> | ||
| + | - Eclipse help <br> | ||
| + | - import WSDL File into Service Registry (SR is running)<br> | ||
| + | - import WSDL File into Service Registry (SR is not running, or SR URL incorrect)<br> | ||
| + | |||
| + | Expectation:<br> | ||
| + | - System tests are passed<br> | ||
| + | - WSDL File is imported into SR<br> | ||
| + | - If SR is not running (or SR URL incorrect) then import ended up with failure<br> | ||
| + | |||
| + | * <b>Code coverage reporting</b> | ||
| + | Demo:<br> | ||
| + | - build's artifact: code coverage report for tooling build<br> | ||
| + | - build's artifact: code coverage report for systemtest build<br> | ||
| + | - build's artifact: merged code coverage reports: tooling build and systemtest<br> | ||
| + | |||
| + | Expectation:<br> | ||
| + | - we have code coverage report after each build<br> | ||
---------------------------- | ---------------------------- | ||
Latest revision as of 10:40, 14 May 2009
Timelines
Sprint duration: 04.May 09 to 19. May 09
Sprint Demo and retrospective: 20. May 09
Ranked User Stories
Here the Ranked user Stories for this sprint:
- Get current results included into Galileo and make it available as Swordfish Milestone on update site.
- JAX_WS services: Code generation WSDL first: S095
- Exemplary Policy processing: S059
- Service Browser for BPEL Editor: B040
- BPEL getting started: B036
- Browse service Registry: A025
- Download from Service Registry: A015
Sprint Goals
Runtime
Goal: Runtime:
Demo scope (2009-05-20):
- Integrate Swordfish and Tools Update Sites into Galileo
- Run vanilla Eclipse M7, use Update installer to install Swordfish Tooling feature from Galileo Update Site
- Create target platform definition and provision Swordfish runtime bundles from Galileo Update Site
- Make PDE build use the new 3rd party projects (Carry forward)
- Run integration tests with PDE build
- Checkout org.eclipse.swordfish.build (and whatever else is required)
- Start 3rd party bundle build
- Start Swordfish build
- Show output of integration tests
- Change ODE version to 2.0 Smila (Carry forward)
- show execution of simple process in ODE
- Exemplary policy processing
- show documentation of sample policy assertion
- Explain implementation
- Demonstrate interceptor in simple test scenario
Tooling
Goal: Tooling: WDSL-first driven development.
- Generate JAX-WS Service Provider from WSDL
Demo:
- Eclipse help
- New Project wizard
- Import wizard
- Cheatsheet
Expectation:
- System tests are passed
- WSDL File is available in the Eclipse Workspase or in the Filesystem
- new JAX-WS Service Provider created
- Running BPEL Editor
Demo:
- Swordfish Wiki documentation (how to get it running with Swordfish tooling)
- Installing BPEL Editor from the Update site
- run BPEL Editor
Expectation (may be will be corrected after first results with BI):
- no QA here.
- BPEL Editor is available for download from update site.
- BPEL Editor installed into Eclipse.
- Registry tooling (SR) integration
Demo:
- Eclipse help
- import WSDL File into Service Registry (SR is running)
- import WSDL File into Service Registry (SR is not running, or SR URL incorrect)
Expectation:
- System tests are passed
- WSDL File is imported into SR
- If SR is not running (or SR URL incorrect) then import ended up with failure
- Code coverage reporting
Demo:
- build's artifact: code coverage report for tooling build
- build's artifact: code coverage report for systemtest build
- build's artifact: merged code coverage reports: tooling build and systemtest
Expectation:
- we have code coverage report after each build
Return to Eclipse Swordfish Sprint Planning