Bug Catcher
Getting started
Try a live Demo
url
https://renataberoli.pythonanywhere.com/
user
renataberoli
password
123and4
About the project
Bug catcher is a pet-project loosely inspired by GitHub Issues and designed with the primary goal of improving my skills in the Django framework.
Sketch
The sketch is the most basic structure I designed within the project. It's an excellent way to put the ideas on paper and start initial tests. Also, working as a developer, I use the sketch to understand the structures of information and draft the models I need to create my system.
The solution
After sketching the interfaces and the system architecture, I translate my sketch into a coding interface with Bootstrap.
Responsive layout
I focused the development on working primarily in desktop systems but was careful to keep minimum responsiveness in mobile devices.
Tech stack
Test cases
Test Cases Plan
Scenario 1 - Login
test_login_failed
| Description | Test Data | Expected Result |
|---|---|---|
| The test aims to check if the user can access the system if the login fails. | Use: username - “beroli”; password - “1234” | The system will return an error asking the user to enter a correct username. |
test_login_success
| Description | Test Data | Expected Result |
|---|---|---|
| The test aims to check if the user will be redirected to the main page if the login is successful. | Use: username - “renataberoli”; password - “123and4” | The user will be redirected to the “list of issues” page. |
Scenario 2 - List filters
test_search_filter
| Description | Test Data | Expected Result |
|---|---|---|
| This test aims to check if the search field works as expected. | Use: Use: “error” as the search argument. | The system will return only issues with “error” in some parts of the title. |
test_priority_filter
| Description | Test Data | Expected Result |
|---|---|---|
| The test aims to check if the priority field works as expected. | Use: Use: “urgent” as the field’s option. | The system will only return issues with “Urgent” priority. |
test_status_filter
| Description | Test Data | Expected Result |
|---|---|---|
| The test aims to check if the status field works as expected. | Use: Use: “closed” as the field’s option. | The system will only return issues with the status “closed”. |
test_all_filters_together
| Description | Test Data | Expected Result |
|---|---|---|
| The test aims to check if all the list filters work together as expected. | Use: search argument - “error”; priority - “urgent”; status - “open”; label - “frontend”; assigned - “renataberoli”. | The system will only show the issue that matches all the filter's arguments. |
Scenario 3 - Create issue
test_issue_creation
| Description | Test Data | Expected Result |
|---|---|---|
| The test aims to check if the issue's creation is working as expected. | Use: title - “Test issue if issue is created”; project - “Acme”; status - “open”; assignee - “renataberoli”. | The system will create a new issue and redirect the user to the detail view. |