In order for the DMC to maintain agile development, due to an ever growing team, we have created a process, using JIRA Software, to allows for easy tracking of task completion to better understand the where a task is in its life cycle. Past tests will be accessible in a Bitbucket repository at the following link:
https://bitbucket.org/DigitalMfgCommons/qa 

JIRA Board Columns

• To Do
• Blocked
• In Progress
• Ready for Testing /Review
• Testing /Review
• Ready for QA
• Quality Assurance
• Ready for MERGE
• Done

Task Life Cycle

To Do

A task is created or pulled out of the JIRA Software backlog and is brought into an active sprint.n The task will show up in the active sprints JIRA Board, in the To Do column. If a developer has completed all their tasks for a sprint, is blocked on all their assigned tasks, or needs to complete a task in that is currently in the backlog, the task will always first show up in the To Do column on the JIRA Board

Blocked

If a developer is unable to continue the work they have made on a task that has been moved into the In Progress column, an is in need of assistance or is waiting for another developer to complete their task first, their JIRA task/card needs to to be moved into this column.

In Progress

When a develper is starting work on a task that has been assigned to them, they should moved the card with their task on it into this column.

Ready for Testing /Review

Once the developer working on the task believes the code is ready to be evaluated, they will perform a final commit of their code and perform a finall git push to their branch, create a pull request in Bitbucket of their branch to the master branch, and then finally move their card into the Ready for Testing /Review column.

Testing /Review

When a lead or senior developer sees that a JIRA card has been moved into the Ready for Testing /Review column they should then move that card into the Testing /Review column when they are reviewing the code. If the code is evaluated and is considered good, the card is then moved into the Ready for QA column. If not the card should have a comment added to it with information as to why the code did not pass review and should then be moved back into the in progress column.

Ready for QA

After a lead developer has reviewed the sumitted code or changes and evaluates it to be good code, the lead developer then moves the JIRA card into the Ready for QA column on the JIRA Board.

Quality Assurance

When the Quality Assurance person sees a card has been moved into the Ready for QA column, they will move the JIRA card into the Quality Assurance column when they are testing the code. The QA person will deploy to code to a QA stack and will look for bug that the new may cause and check to see if the code completes the task the JIRA cardi s there to represent. If the code appears to be good, the card is then moved into the Ready for MERGE column, and a comment is added to the card to note what is working. If the task seems to somewhat work but not fully, or if the task seems to work but something else seems to have stopped working properly, then the QA person will reach out to the developer and will ask them if the code can be easily updated and fixed, then the developer will make the necessary fixes and the QA person will go redeploy the code to the QA stack and check if everything seems to be in order. If the Changes are not easily fixable, the QA person will add a coment to the card regarding what is not working, and move the card back into the In Progress column.

Ready for MERGE

The Senior/Lead Developer sees that a JIRA card is in the Ready for MERGE column on the JIRA Board, the code will recieve one more pass before the code is merged in to the master branch. If the code does not pass the final inspection, the Senior Developer will add a comment to the card regarding what they believe is missing or is incorrect, and will move the card back into the In Progress column. If the Merge to the master branch is successful, the JIRA card is moved into the Done column and will be removed from the JIRA board after the sprint is complete.

Done

When the Senior/Lead/Head Developer has evaluated the submitted changes or code and decides the code is okay to be added to the master branch of the repository, the task/JIRA card is moved into this column and task is now considered done.