The document outlines requirements for an expenses tracking system, including functionality requirements for users to log in and add new expenses with date, category, label, amount, optional description, and receipt upload. It also requires storing additional metadata like username, date/time, and initial status. Dev-ops requirements include the app being deployed to a cloud service and using git hooks for quality. Testing requirements include writing three unit tests using the AAA pattern.
The document outlines requirements for an expenses tracking system, including functionality requirements for users to log in and add new expenses with date, category, label, amount, optional description, and receipt upload. It also requires storing additional metadata like username, date/time, and initial status. Dev-ops requirements include the app being deployed to a cloud service and using git hooks for quality. Testing requirements include writing three unit tests using the AAA pattern.
The document outlines requirements for an expenses tracking system, including functionality requirements for users to log in and add new expenses with date, category, label, amount, optional description, and receipt upload. It also requires storing additional metadata like username, date/time, and initial status. Dev-ops requirements include the app being deployed to a cloud service and using git hooks for quality. Testing requirements include writing three unit tests using the AAA pattern.
The document outlines requirements for an expenses tracking system, including functionality requirements for users to log in and add new expenses with date, category, label, amount, optional description, and receipt upload. It also requires storing additional metadata like username, date/time, and initial status. Dev-ops requirements include the app being deployed to a cloud service and using git hooks for quality. Testing requirements include writing three unit tests using the AAA pattern.
Functionality Users need to be logged in to see the system.
Anyone not logged in should be redirected to the Login screen. When a user is logged in they should see an Add expenses button or link. This sends them to a screen where new expenses can be added. This should ask the user for: 1. The date (this should default to the current date and be selected using a date picker). 2. A category to be picked from one of the following four categories: travel, food & drink, accommodation, other. 3. A short label (used on the home screen). 4. A box where the user enters the amount being claimed. 5. An optional multi-line description of the expense that supports Markdown formatting. 6. An upload tool to upload a scanned copy of the receipt from the User's computer. In addition to this data, the database should also store: 1. The username of the person adding the item. 2. The current date and time. 3. The status of the expense which should be set to not-approved Dev-Ops Latest app deployed to cloud service. Simple Git Hook added and used to improve code quality Test Three useful unit tests written using the AAA pattern