Run unit-tests for each commit into Merlin repo

Registered by Timur Sufiev

It is clear that comprehensive set of unit-tests is the only way to guarantee that new features/fixes of bugs don't break an existing functionality of a project. It is needed to identify the areas of Merlin/Mistral that should be covered with tests, write the sufficient set of tests and create Jenkins jobs that will be run on each check/verify.

Blueprint information

Status:
Complete
Approver:
Timur Sufiev
Priority:
High
Drafter:
Timur Sufiev
Direction:
Approved
Assignee:
Paul Karikh
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Timur Sufiev
Completed by
Timur Sufiev

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bug/1428768,n,z

Addressed by: https://review.openstack.org/169308
    Move out Merlin and Mistral code into separate modules

Gerrit topic: https://review.openstack.org/#q,topic:add_karma,n,z

Addressed by: https://review.openstack.org/170902
    Add karma testing

Gerrit topic: https://review.openstack.org/#q,topic:bp/merlin-unittests,n,z

Addressed by: https://review.openstack.org/174957
    Add stubs for merlin.utils unit-tests

Addressed by: https://review.openstack.org/176271
    Fill Merlin filters unit-test suite with actual code

Gerrit topic: https://review.openstack.org/#q,topic:bug/1446230,n,z

Addressed by: https://review.openstack.org/176406
    Enable changing Task structure

Addressed by: https://review.openstack.org/177389
    Add unit-tests for merlin directives

Gerrit topic: https://review.openstack.org/#q,topic:filters_merlin_tests,n,z

(?)

Work Items

Work items:
- Write unit-tests: DONE
- Create Jenkins jobs: DONE

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.