...

In the OpenNCP development project we lack a dedicated test team.  Normally there would be test specialists who do test planning and conduct system tests during a sprint.  This is followed by acceptance test when the software goes through a cycle of QA and bug fixing.  I’ve always thought it strange that we don’t follow this practice

...

• OpenNCP 1.1.1 Release
  • Longer Code Freeze > for Quality Assurance
  • Norbert, Stéphane
  • Konstantin: More unit tests, less regression test;

3. Development Status

• HCER-Client:
  
  • Konstantin: meeting: request to GNOMON for GUI implementation > that Marcello is checking with Gnomon
  • Marcello: negotiation with Gnomon; risk of stop the development of HCER tool - negotiation with PMT and project coordinator;
  • Marcello: conversation with Gnomon regarding LRT and MTC, to manage effort;
  • Konstantin: CDA Specifications and content are clear;
• HCER-Server:
  • The implementation is ready, and can be committed;
    • DON'T include AUDIT messages, because they can break some  
  • Changes are been committed to the development
  • Ready for integration with the HCER-Client.
  • Fonseca: add some comments in the client connector -share them;
• PAC:
  • Key task: Adjust Server side to support new assertions:
    • We can now accomplish task when we have resources available.
• OpenNCP
  • Portal, TM and TSAM: for sustainability, SHOULD be ready for improvement without of the initial providers.
    • Steen already done improvements in the past and ask for review for the initial  providers.
    • BUT:

NEXT Steps

...