ktzy0305 / eti-to-do-app Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 1.76 MB

ETI CA2

Python 77.32% HTML 20.72% CSS 1.97%

eti-to-do-app's Introduction

👋 Hi, I’m @ktzy0305
👀 I’m interested in Decentralized Apps!
🌱 I’m currently learning Rust, Assembly
💞️ I’m looking to collaborate on interesting projects!
📫 How to reach me
- Email: [email protected]

eti-to-do-app's People

Contributors

Watchers

eti-to-do-app's Issues

QA: Write Test Case for To-Do page

Similar to the previous issue for writing test cases for the login page, come up with some test case for the To-Do page

Sprint 2: QA Test Case Scenarios

Write Test Case Scenarios to meet the acceptance of Sprint 2 Requirements to cover the following issues:
#14
#15
#16
#17
#18

Sprint 2: Team member roles allocation and tasks assigned for Sprint 2 to be added to Team Contributions Page

Issue on Django database

@ktzy0305, Test data save in @tanjunwu for To-do item page is not shared among git after pulling the file.
Thanks!

Navigation Bar for easier access between To-Do, To-Do History and Team Contribution pages.

Testing of To-Do History Page

Prepare test scenarios for the To-Do History Page

Sprint 2: User Login Page should also allow new users to sign up

Sprint 1: User Login Page should allow predefined valid users to log in

This is a feature for users to log in to the To-Do application so that they are authorized to see all the To-Do items.

Improve Test Coverage

Let's try to boost our current test coverage since we are done with the requirements.

Sprint 2: Addition and deletion of To-Do items auto archived instead of the current manual process

Testing of User Login Page

Prepare test scenarios for the login functionality

Sprint 1: The To-Do Page should contain options to delete, add, archive to history.

The To-Do Page should contain options to delete, add, archive to history. These options should come in the form of buttons.

test_cat.py in QA Folder

Hi all, May I know what is the "test_cat.py" in QA folder does?

Many thanks.
Malcolm

QA: Perform testing on To-Do page

Since @tanjunwu has completed the To-Do Page should contain options to delete, add, archive to history at 40619ed you can commence testing on that

Sprint 2: QA Automated Tests (Pytest + Selenium)

Write Pytest and Selenium code to automate the test case scenarios in issue #21

Sprint 2: To-Do Page should have To-Do items filtered to only showing those that were created by them

Testing of To-Do Page

Prepare test scenarios for the To-Do page

QA: Write Test Case for User Login Page

Description

For this request, write out at least 3 test cases for User Login Page. It must contain both "Failing" and "Passing" test cases. Leave the results and justification empty as this is for later when you will be performing testing on the application to get the testing results.

Example:

Sprint 2: To-Do History Page should now show a history of all To Do items added and deleted.

I believe feature would be implemented similar to how user audit logs will look like.

Example

History:
To Do Item 4 was deleted. Timestamp: 18:20
To Do Item 7 was created. Timestamp: 18:22

Sprint 1: The To-Do Page should contain all To-Do items to be shown to valid User after log in regardless of the owner of the To-Do items.

The To-Do Page should contain all To-Do items to be shown to valid User after log in regardless of the owner of the To-Do items.

Sprint 1: The Team Contributions Page should include all team member roles allocation and tasks assigned for this activity.

The Team Contributions Page should include all team member roles allocation and tasks assigned for this activity. It can be done in the form of a table.