Marvin and Automation Team Tasks

Status: From last few weeks till November 1st 2013.

Items completed:

1. Bug Fixes\Enhancements:
We did few bug fixes to Marvin. Debugged, analyzed and fixed bug fixes to Marvin.
Did code clean up in various areas under Marvin.
Enhancements as per request to Marvin. Enhanced few libraries\utilities for easy testing.
Added bugs to Jira for bug fixes.
Few patch submissions for enhancements
Did few nosetests plugin changes.
Marvin Refactor enhancements, testing the changes. ETA: Should be finished by end of this week.
Added enhancements to documentation, fixing documentation issues.
Educating the QA\Team for cleaner reviews.
We raised few bugs against product.

2. Reviews:
Tracking weekly review list.
Working with reviewers to get the reviewers issues fixed, Marvin changes required.
Did group reviews, reviewed feature tests, submitted issues, raised few patch submissions.
Closed and Submitted few review patches.

3. Misc:
Helping team with Marvin issues raised in ML,or otherwise to QA.
Fixed few issues reported.
Meetings and Misc tasks.
Jenkins: Setting up,Identifying of issues related to jenkins runs, fixing few flows etc

Items Planned for coming week:
Raising and fixing issues for Marvin..
Enhance logging support to Marvin. Current logging is not clean enough.
Helping team with new infrastructure related changes.
Adding config support to Marvin. Currently, there is no way to get clean configuration driven tests. We are planning to add this support to Marvin.
Support parallel deployment for new infrastructure support, logged a bug to track this, this request was raised from team for new infrastructure support. Requires some good effort on this change and testing.
Cleaning up of code, there were few areas where we are cleaning up unwanted code wherever is necessary and modularizing the structure.
Getting clean reviews and zero script errors. ( This is one of the goal, ultimately script errors should be zero )
Removing hard coding of values and separation from code. Currently, there is an issue raised from QA team and working to fix these as well.
Simulator changes. We already raised our availability to Alex\Sudha for further discussions. Plan is to start meeting on those to kick start to put up the plan and start implementing those changes.
Plan to study,work and get code coverage for CS using integration tests, we need to spend some time on getting code coverage tools and analysis using python.
Help in enhancing unit test code coverage wherever possible for CS. Enhancements to unit testing is a long term goal to get more coverage and release less bugs to QA.

Note: The list of bugs raised, fixed and patch submissions done should be available under jira\review board,components "Marvin\Automation" under cloudstack. We can provide them here if required.