The unit tests do not cover exceptional cases e.g. invalid user input.

These files look like Behave features. what are they doing in the root directory of the repo?

Register form does not have a confirm password field which should protect from typos.

The user may record activities which occur on a field of a farm they work on.
A resource use and date is recorded with the activity and if the activty is a harvest then the user will be redirected to add the crop harvest to the produce section for sale.

Farmer should be able to define their own process for a crop. This should capture a schedule of activities that are required to produce the crop.

Improve at least statement coverage.

I want to reuse some code to help my own work.
But I am confused about those python files. I have no idea which file does what without reading all code first.
Would anyone mind adding descriptions to better explain which file does which part of work?

How nice of you to commit and reveal the secret key in the repository and open our system to hacks.
Consider how to do this in Production and Dev settings.

One single "steps" file is not easy to manage and as more feature being added, that file will eventually become too long and error prone.

(Don't know if I can raise an issue)

some important parts of main.py are not covered by the unit tests.

An Exception is thrown when running the behave test in features/add_produce.feature

stack trace:
i.e. Error on request:
Traceback (most recent call last):
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/werkzeug/serving.py", line 193, in run_wsgi
execute(self.server.app)
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/werkzeug/serving.py", line 181, in execute
application_iter = app(environ, start_response)
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/flask/app.py", line 1836, in call
return self.wsgi_app(environ, start_response)
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/flask/app.py", line 1820, in wsgi_app
response = self.make_response(self.handle_exception(e))
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/flask/app.py", line 1403, in handle_exception
reraise(exc_type, exc_value, tb)
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/flask/_compat.py", line 33, in reraise
raise value
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/flask/app.py", line 1817, in wsgi_app
response = self.full_dispatch_request()
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/flask/app.py", line 1478, in full_dispatch_request
response = self.make_response(rv)
File "/Users/whwong/repos/teaching/info9117/asgn/asgn_env/lib/python3.5/site-packages/flask/app.py", line 1566, in make_response
raise ValueError('View function did not return a response')
ValueError: View function did not return a response

unit tests do not cover exceptional cases.

Formulate a requirements.txt file for pip3 to automatically install project library dependencies.
i.e.
pip2 install -r bluegarden_requirements.txt

consider different requirements for dev, testing and production.

Please remove this file.

tests do not cover exceptional cases for login and register

Please improve at least statement coverage for this.

bluegarden.db is committed to the repository. This tracks local changes to the repository.
Look to remove it from the repository

All unit tests are currently thrown into test.py.
Consider reorganising this into a test directory of multiple test files