Sprint 129 Progress Summary
Apr 7 - Apr 21, 2014
Executive Summary
Overall Status
Sprint status is excellent. The Product team prioritized and completed the following themes and tasks for Sprint 129 comprising 38 points. These themes included - community support post release and beginning work for new feature development - Direct, Admin GUI. The team also supported and participated in the CONNECT CCB to understand priorities and high level requirements from the federal partners.
A few tickets were added during the course of the sprint for tasks that the team deemed necessary to support either development of the new features or support the community - this brought the sprint point total to 41. These include - an issue found with event logging (CONN-1045) that was discovered as part of the Admin GUI feature. Also research into the HeartBleed bug and its impact was included (CONN-1053, 1059). A small bug in the DocQuery adapter was fixed (CONN-1061).
The team completed 38 points this sprint. The tickets that were not completed and will be moved over to the next sprint are CONN-952 (Supporting VA with 4.2.1 upgrade) and CONN-998 (Testing the Direct config services). CONN-952 was moved to the next sprint since VA moved their CONNECT development upgrade work over to the next week .
Burndown
Sprint Themes and related tickets for Sprint 129:
- Community Implementation support
- Responded to forum posts - http://www.connectopensource.org/developer-resources/forums
- Research to assess impact of Heatbleed/Heartbeat bug (CONN-1053)
- Determined there are not any security risks to CONNECT adopters using supported application servers
- Next Release (4.4)
- New Features for next release
- Direct enhancements
- As a CONNECT developer I want to analyze Direct functionality and design an approach to creating test scripts in order to have functional level testing coverage of Direct (CONN-1010)
- Created a story plan for Direct service that defines the Main and Alternate paths to determine the acceptance criteria for the service.(CONN-1022)
- This will be refined further as more development work is accomplished and should help out with test/regression scripting as Direct is being enhanced.
- Analyzed and researched options to test Direct from a regression perspective (CONN-1031)
- Created a POC to determine SOAPUI 4.5.x with Java Mail jars can be leveraged for regression automation.
- Separate mail accounts/mail boxes can be created to simplify automated testing for Sending STA so that we can test with multiple Direct environments.
- Separate Recipient email account in the Receiving STA (amazon Direct RI instance) can also be accomplished at the receiving end for automated testing.
- Analyzed how event logs could be used to test Direct as well as how Direct can be performance tested.
- Research findings are documented in the ticket.
- Created a POC to determine SOAPUI 4.5.x with Java Mail jars can be leveraged for regression automation.
- Created a story plan for Direct service that defines the Main and Alternate paths to determine the acceptance criteria for the service.(CONN-1022)
- Refactor Direct as a service (CONN-997)
- Create and expose interfaces via java + web services to process direct messages. Implemented sendDirect and ReceiveDirect as web services.
- Create Direct configuration services in the CONNECT tech stack
- Implemented Spring/Hibernate Direct configuration services as part of CONNECT to enable changing Direct config settings through the Admin GUI(CONN-1034)
- Inject services into the wsdls (CONN-1033)
- Testing of this user story will be completed next sprint
- As a CONNECT developer I want to analyze Direct functionality and design an approach to creating test scripts in order to have functional level testing coverage of Direct (CONN-1010)
- Administrative GUI enhancements
- Created a backing bean to pull the data from a mock service that demonstrates the remote gateways the local gateway communicates with, including number of transactions (CONN-1028, CONN-1023)
- Create the Admin GUI page/xhtml for displaying the information from the backing bean(CONN-1027)
- Direct enhancements
- Bug fixes and other improvements this sprint
- Adding missing sender/receiver values to event logging to help display number of transactions in Admin GUI(CONN-1045)
- Fixed bug related to Doc Query Adapter pre-pending extra prefix to ExtrinsicObject Home(CONN-1061)
- Improved the script for Transaction Id test as it failed to consistently work if run first in pass-through and then in standard mode in an automated test environment(CONN-1020)
- New Features for next release
- Ongoing Custodial Agent Duties
- CONNECT 4 Blogs and Forum posts
- Participated in the Change Control board to discuss priorities and requirements for the federal partners.
JIRA Planning Board of Committed User Stories for Sprint 129
Completed Tickets
Tickets not completed
