JIRA and Testing
JIRA basic 6 steps
1. Create a project
2. Select a template
- scrum - used for sprint wise task
- kanban - track the Epics status release wise
3. Setup board
4. Create issues - will go in backlogs
- Initiative - are collections of epics that drive toward a common goal.
- Epic - an “epic” is a large body of work that can be broken down into smaller Stories and not completed in a sprint.
- Story - Stories further divided into tasks, QA, Spike. Stories are distributed in multiple sprints
- Task - Digging down the story in small tasks. All tasks in a story sould be completed in a sprint. Many subtasks can be created under tasks
- Bug - Defect reporting
- QA - QA tasks - Automation code for E2E test. Completed in a sprint
- Spike - To take knowledge
- Investigation - Troubleshooting
5. Invite your team
6. Setup my workflow
- To Do
- In Progress
- In Testing
- In Review
- Done
Reports
- Burndown chart
- Sprint report
1. Create a project
2. Select a template
- scrum - used for sprint wise task
- kanban - track the Epics status release wise
3. Setup board
4. Create issues - will go in backlogs
- Initiative - are collections of epics that drive toward a common goal.
- Epic - an “epic” is a large body of work that can be broken down into smaller Stories and not completed in a sprint.
- Story - Stories further divided into tasks, QA, Spike. Stories are distributed in multiple sprints
- Task - Digging down the story in small tasks. All tasks in a story sould be completed in a sprint. Many subtasks can be created under tasks
- Bug - Defect reporting
- QA - QA tasks - Automation code for E2E test. Completed in a sprint
- Spike - To take knowledge
- Investigation - Troubleshooting
5. Invite your team
6. Setup my workflow
- To Do
- In Progress
- In Testing
- In Review
- Done
Reports
- Burndown chart
- Sprint report
Comments
Post a Comment