-
Notifications
You must be signed in to change notification settings - Fork 3
Development Manual
Shira Segal edited this page Feb 25, 2018
·
6 revisions
To access the code send an email to group with an explanation why do you need the code, and how would you help the application to improve.
- If a bug was discovered please report us by opening a bug issue, or massege us in gitter chat (link in the main README) and we will take care of it.
- We use firebase database.
- We are using git via GitHub for version control.
- Build Notes: written in wiki page.
- Test- we will build set of tests and keep them running during development to insure correct functionality.
- After every iteration we will have a relase when the last one will be presented to the client for feedback and finalchanged (no difference between release and debug version).
- Put attention - The application will not work without internet conection.
- BUG- there will be in the github a project tab upon entry will see all bug listed the bug column as well as done part and in progress. in order to work on it assign yourself .
- Integrity checks for input using built-in input formats.
- Handling unusual cases such as input too long, and various inputs such as not entering value in a place that allows it, giving a default value
- Mandatory provision of mandatory fields.
- When a user is identified only he can create a recipe, edit a new recipe and share a recipe. It should have happened that when a user login to the system then security and authentication would be stronger (possible through Google)
Copyright 2017 by JCE - Jerusalem College Of Engineering
There is no copy, duplicate, or spreading the code without promotion of any kind. for more detail about using our app, please visit the application README