Page History

...

The product owner makes sure the work of the brigade is relevant to the operator.  It is similar to the role as defined in agile scrum. In short, they make sure the features are defined from the end user perspective, and they make sure that work is done in priority order. The product owner provides "pull" for features from the team - helping to bring the work into use in the network. One can find more information on the web about the role of a product owner. One such page is here.

Test Coverage

Test Coverage is an important aspect for stability of ONOS.  Test Coverage includes both Unit Tests and System Tests. 

For details on unit test coverage refer to Unit Test criteria and guidelines.

System Test Coverage includes delivery of detailed test plans and that is shared with the team for reviews.  Critical and Major functional test scenarios are to be targeted for automation.  Automated tests/scripts to be submitted into the common repository.  Committing test cases to a common repo will help the community/users to scale the tests in future.  All test cases that are automated need to be run before and after code merges into the mainstream. Once code merges to the mainstream, automated test scripts need to be integrated to jenkins QA jobs for continuous regression of the features.

ON.Lab test engineer(s) will collaborate with the testers in the brigade and guide through the test coverage procedures.  Testers on the brigade team can also take advantage of the existing automation framework and tools that ON.Lab uses for system tests.

Refer to System Testing Guide for more detailsSuchitra to add information about the test coverage requirements and how the ON.Lab QA team will interact with brigades here...