Explore

f23 MAD5234 Assignment 1 Create your own Bugzilla

Bugzilla is an industry standard tool for tracking and processing software product defects.

⁠

Loading…⁠

⁠

How to hand in:

Put your TRELLO Board LINK into a text file.

Named as StudentName_StudentID.txt

Remember to make

peter@petersigurdson.net⁠

a member of your TRELLO Board.

Upload your TEXT file to:

https://www.dropbox.com/request/cnjv4KWYolAz7XMW5O4o⁠

⁠

f23 MAD5234 Assignment 1 Create your own Bugzilla

Learning Outcomes:

Both either TRELLO Version - OR - GIT ISSUES Version.

Leverage TRELLO - or - GitHub Issues and GitHub Actions to build a simplified bug tracking system

Understand the usage of distributed version control platforms for software quality control.

⁠

Assignment: (one option) Building a Bug Tracking System Using Trello Boards

⁠

Objective:

To develop an understanding of how modern project management tools can be used for bug tracking.

By the end of this assignment, you should be able to utilize Trello boards effectively to track, categorize, and manage software bugs, while also integrating with GitHub for seamless software development. Note: With a paid TRELLO Subscription, you can a GITHUB POWERUP in TRELLO: You will get a notification in TRELLO of monitored changes to the GITHUB repository. (code commits/changes).

⁠

Instructions:

Setting Up a Trello Board

Trello⁠

if you haven't already.

Create a new board and name it appropriately (e.g., "Bug Tracking for [Your Project]").

Within your board, set up the following lists:

To Do: For new bugs/issues that have been reported.

In Progress: For bugs/issues that are currently being addressed.

Resolved: For bugs/issues that have been fixed but are awaiting verification.

Verified: For bugs/issues that have been fixed and confirmed.

Closed: For issues that are either irrelevant, duplicates, or will not be addressed.

Using Trello for Bug Management

Take MathFactory application. Invent some some problems. Demonstrate processing the solution of them.

When a new bug is reported, create a card in the To Do list.

Attach necessary details: error logs, screenshots, steps to reproduce, expected behavior vs. actual behavior. (See Bugzilla tutorial for ideas).

Use labels for categorization: severity (low, medium, high, critical), type (UI, backend, database), etc. Review in PPTX the contexts of TESTING. Includes for those defects in your TRELLO defect tracking form.

Assign @members to specific bugs as they work on them, moving the card to In Progress.

As bugs are addressed, move them to Resolved, and after verification, to Verified.

Documentation and Best Practices

Establish a consistent process for reporting and addressing bugs.

This can be in the form of a document pinned to the board or saved in a prominent place for all team members.

Encourage regular reviews of the board, especially the To Do and In Progress lists.

⁠

Grading Rubric:

Setup and Structure (30 points)

Proper setup of Trello board with appropriate lists (10 points)

Effective use of labels for categorization (10 points)

Documentation of processes and best practices (10 points)

Seamless creation of Trello cards when GitHub issues are opened (20 points)

Effective use of GitHub Actions for integration (20 points)

Bug Management (20 points)

Consistent and effective management of bugs using the Trello board (10 points)

Appropriate use of cards, including all necessary details (10 points)

Overall Presentation and Flow (10 points)

Clarity, organization, and overall flow of the board and its contents (10 points)

⁠

Remember, the aim of this assignment is to familiarize you with the concept of using project management tools for bug tracking.

While Trello is the tool of choice in this assignment, the principles can be adapted to many other platforms. Explore, experiment, and find the best practices that suit your project's needs.

You can do this with EITHER TRELLO or GIT issues, you do not need to do both!

Assignment <Alternate Version>: Bug Tracking System Using GitHub Issues and Actions

Objective:

Enhance your understanding of software testing, bug tracking, and quality assurance using modern tools like GitHub. Your task is to set up a TRELLO BOARD as a bug tracking system. To take it further, integrate GitHub Actions for automated notifications or processes when issues are raised or updated.

Instructions:

Repository Setup: Create a new TRELLO Board. This repository will act as your project where bugs and issues will be tracked.

GitHub Issues for Bug Tracking:

Familiarize yourself with creating, editing, and closing issues on GitHub.

Define labels for prioritization (e.g., High, Medium, Low).

Use milestones for version or sprint tracking.

Understand the difference and usage of Assignees vs. Reviewers.

Notifications with GitHub Actions:

Set up a basic workflow using GitHub Actions that sends an automated comment or notification whenever a new issue is raised or an existing issue is updated.

Explore how you can integrate external communication tools (e.g., sending an email or a Slack message) when certain events occur.

Documentation:

Prepare a user guide explaining how to use your GitHub Issues setup as a bug tracking system.

Create a technical guide detailing your GitHub Actions workflows, triggers, and actions used.

Reflection: Write a short reflection (500 words) on:

The feasibility and scalability of using GitHub Issues as a primary bug tracking tool.

Advantages and limitations compared to traditional systems like BUGZilla.

Your experience with automating processes using GitHub Actions.

Grading Rubric:

Repository and GitHub Issues Setup (30 points)

Proper labels, milestones, and issue templates: 20-30 points.

Basic setup with some missing elements: 10-19 points.

Minimal or incomplete setup: 1-9 points.

GitHub Actions Integration (30 points)

Comprehensive workflows for multiple events: 20-30 points.

Basic workflows for 1 or 2 events: 10-19 points.

Minimal or no GitHub Actions integration: 1-9 points.

Documentation (30 points)

Comprehensive, clear, and well-structured documentation: 20-30 points.

Basic documentation with some elements missing: 10-19 points.

Minimal or no documentation: 1-9 points.

Reflection (10 points)

Insightful, comprehensive reflection: 7-10 points.

Basic reflection with some insights: 4-6 points.

Minimal or no reflection: 1-3 points.

Total Points: 100

Submission:

Submit the link to your GitHub repository, user, and technical documentation, and reflection in the assignment portal.

Deadline: [Insert Date]

This assignment is designed to ensure you grasp the practical applications of modern tools like GitHub in real-world software testing and quality control environments. Good luck!

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.