Post install tests to meet EC CMO requirements
Registered by Yves Pelletier on 2009-11-16
In order to present the EC Software Management Board and Configuration Management Office with a release version of libECBUFR, we need to implement basic post-installation tests that confirm it is working as expected.
Blueprint information
Status:
Not started
Approver:
None
Priority:
Not
Drafter:
None
Direction:
Needs approval
Assignee:
Chuck Paterson
Definition:
Review
Series goal:
None
Implementation:
Unknown
Milestone target:
milestone icon 0.8.2b2
Started by
Completed by
Related branches
Related bugs
Sprints
Whiteboard
Marked as essential because it is a CMO requirement. This needs to be tied in with the binary installation. The .deb package would contain one or two BUFR messages, BUFR tables, and matching text decode. The newly installed package would decode the BUFR, match the decode against the one provided, then re-encode and match the new BUFR message against the one provided.
2010-11-26: at the BUFR WG it was indicated that ongoing automatic regression testing and debian package production constitutes a form of automated quality assurance. The CR to SMB will be drafted by Y. Pelletier and C. Paterson in coming days; post-install tests will be addressed, but not necessarily in the manner illustrated in the above paragraph.
Moved from https://blueprints.launchpad.net/libecbufr/+spec/post-install-tests
Post install tests to meet EC CMO requirements Registered by Yves Pelletier on 2009-11-16
In order to present the EC Software Management Board and Configuration Management Office with a release version of libECBUFR, we need to implement basic post-installation tests that confirm it is working as expected.
Blueprint information
Status: Not started
Approver: None
Priority: Not
Drafter: None
Direction: Needs approval
Assignee: Chuck Paterson
Definition: Review
Series goal: None
Implementation: Unknown
Milestone target: milestone icon 0.8.2b2
Started by
Completed by
Related branches Related bugs
Sprints
Whiteboard
Marked as essential because it is a CMO requirement. This needs to be tied in with the binary installation. The .deb package would contain one or two BUFR messages, BUFR tables, and matching text decode. The newly installed package would decode the BUFR, match the decode against the one provided, then re-encode and match the new BUFR message against the one provided.
2010-11-26: at the BUFR WG it was indicated that ongoing automatic regression testing and debian package production constitutes a form of automated quality assurance. The CR to SMB will be drafted by Y. Pelletier and C. Paterson in coming days; post-install tests will be addressed, but not necessarily in the manner illustrated in the above paragraph.