You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

REQ JiraREQ Test TaskTest Plan StatusTest Plan Link (y/n)Notes
REQ-347REQ-455In process(tick)
REQ-334REQ-454In process(tick)
REQ-318REQ-452In process(tick)
REQ-319REQ-451In process(tick)
REQ-320


This Use Case is Modeling work only, there is no S/W development or Testing
REQ-321REQ-450In process(tick)
REQ-345REQ-449In process(tick)
REQ-322REQ-449In process(tick)
REQ-327REQ-448Done(tick)
REQ-352REQ-447Done(tick)Linked to general documentation instead of test plan.
REQ-381REQ-445In process(error)
REQ-324REQ-444In process(tick)
REQ-342REQ-436In process(tick)
REQ-325REQ-435Done(tick)
REQ-331REQ-434Done(tick)Test plan embedded in Jira
REQ-341REQ-426In review(tick)
REQ-332REQ-332Done(tick)Test plan embedded in Jira description of REQ-332
REQ-335



REQ-336



REQ-337



REQ-338



REQ-339


As CNF orchestration in ONAP is getting introduced in this release, and CNF requiremets are getting stablised in OVP 2.0, its appropriate to move this to next release to add support for compliance check of CNF and related features.
REQ-353


There was no development work related to this requirement in Guilin release. Thus also no integration tests.
  • No labels