Unit testing. A unit test focuses on a single “unit of code” – usually a function in an object or module. By making the test specific to a single function, the test should be simple, quick to write, and quick to run. This means you can have many unit tests, and more unit tests means more bugs caught.
Non-functional testing concerns software issues that are not necessarily associated with a particular function or user action. This includes performance, reliability and usability issues. Basically, non-functional tests analyze how a system deals with unexpected inputs. This also includes security testing. So to answer the initial question
Functional Test - a test that checks the functionality as opposed to e.g. Performance. This can be a unit test as well, but since this terminology is mostly used by QA - when people talk about them they usually mean Functional System Test. Note, that different authorities may use different definitions of the same terms. A test that serves to verify the functionality of a single, cohesive unit of code is called a unit test. Unit tests are independent and typically run in seconds or minutes; if they take longer to execute, you’re likely not writing unit tests. Unit tests should be written by developers to assert the correct operation of source code.4. While the goals of code unittesting and functional/non-functional testing are worlds apart, the python unittest module can lend itself as a framework for QA testing and unittesting. Robot framework was designed from the ground up for QA testing with hooks into languages such as Python/Java. Robot framework works well for tabular test cases
Kye6EK.