E-mail id: divyam096@gmail.com
The assignment demonstrates the application of scopes, which is applicable with respect to a variable name, and closures (also known as nested functions) in Python codes.
This closure has been written to check if the docstring of an input function has greater than fifty characters.
check_docstring()
Brief description of all the test cases that have been employed to check the efficacy of the algorithms written within the function “check_docstring” are as follows:
| Name of the test | Brief description of the test | Status (Passed/ Failed) |
|---|---|---|
| test_session_6_check_docstring_no_function | This test checks if the code raises an error when a non-integer value is passed. | Passed |
| test_session_6_check_docstring_no_docstring | This test checks if the code raises an error when no docstring is passed. | Passed |
| test_session_6_check_docstring_less_than_50_characters | This test checks if the code raises an error if a docstring containing less than fifty characters has been passed. | Passed |
| test_session_6_check_docstring_greater_than_50_characters | This test checks if the code throws any execution error when an actual docstring containing more than fifty characters is passed. | Passed |
This closure has been written to check if an input number is a Fibonacci one and to generate the next Fibonacci number.
get_fibonacci_number()
Brief description of all the test cases that have been employed to check the efficacy of the algorithms written within the function “get_fibonacci_number” are as follows:
| Name of the test | Brief description of the test | Status (Passed/ Failed) |
|---|---|---|
| test_session_6_get_fibonacci_number_type_check | This test checks if the input number is greater than zero; the test also checks if the number is an integer; the test also checks if the number is a Fibonacci one. | Passed |
| test_session_6_get_fibonacci_number_execution_check | This test checks if the next Fibonacci number generated is correct. | Passed |
This closure has been written in order to count how many times a few allowed functions - 'add', 'mul' and 'div' - have been called, and the respective counts are stored as values in a dictionary, with the corresponding function names acting as the keys.
track_arth_count(fn), where, fn = a function that needs to be passed as a mandatory positional argument.
Brief description of all the test cases that have been employed to check the efficacy of the algorithms written within the function “track_arth_count” are as follows:
| Name of the test | Brief description of the test | Status (Passed/ Failed) |
|---|---|---|
| test_session_6_track_arth_count_dict_check | This test checks if the output is being stored in a dictionary. | Passed |
| test_session_6_track_arth_count_no_fn | This test checks if positional argument exists in the function track_arth_count. | Passed |
| test_session_6_track_arth_count_no_args | This test checks if the required positional arguments have been passed to the track_arth_count inner function. | Passed |
| test_session_6_track_arth_count_invalid_arg | This test checks if the input is a valid function. | Passed |
| test_session_6_track_arth_count_undefined_function | This test checks if an error is raised when a disallowed function is passed as an argument. | Passed |
| test_session_6_track_arth_count_function_execution_test | This test checks if the functions are giving appropriate results after execution. | Passed |
This closure has been written to take a dictionary - similar to the one created in the function track_arth_count - as input, and counting the number of times 'add', 'mul' and 'div' have been called.
new_input_dictionary(fn, custom_dict) where, fn = a function that needs to be passed as a mandatory positional argument, custom_dict = dictionary input by the user.
Brief description of all the test cases that have been employed to check the efficacy of the algorithms written within the function “new_input_dictionary” are as follows:
| Name of the test | Brief description of the test | Status (Passed/ Failed) |
|---|---|---|
| test_session_6_new_input_dictionary_dict_check | This test checks if the output is being stored in a dictionary. | Passed |
| test_session_6_new_input_dictionary_invalid_arg | This test checks if the input is a valid function. | Passed |
| test_session_6_new_input_dictionary_no_args | This test checks if the mandatory positional arguments have been passed in function new_input_dictionary. | Passed |
| test_session_6_new_input_dictionary_inner_no_args | This test checks if the mandatory positional arguments have been passed in the inner function of new_input_dictionary. | Passed |
| test_session_6_new_input_dictionary_undefined_function | This test checks if an error is raised when a disallowed function is passed as an argument. | Passed |
| test_session_6_new_input_dictionary_function_execution_test | This test checks if the functions are giving appropriate results after execution. | Passed |
The following table illustrates the test cases that have been employed to check the various aspects of document formatting of the README.md and the session6.py files.
| Name of the test case | Brief description of the test case | Function/File being tested | Status(Passed/Failed) |
|---|---|---|---|
| test_session5_readme_exists | This test checks if the README.md file has been created. | README.md | Passed |
| test_session5_readme_500_words | This test checks if the README.md file contains at least 500 words. | README.md | Passed |
| test_session5_readme_proper_description | This test checks if the functions have been described well in the README.md file. | README.md | Passed |
| test_session5_readme_file_for_more_than_10_hashes | This test checks if a minimum of ten topics have been mentioned in the README.md file. | README.md | Passed |
| test_session5_indentations | The PEP8 guidelines state that the number of spaces left should be a multiple of four, for defining proper indentation within a code. This test checks if the code has been written adhering to the aforementioned guideline. | session5.py | Passed |
| test_session5_function_name_had_cap_letter | According to PEP8 guidelines, the names of functions cannot have any capital letters in them. This test ensures that there are no such capital letters in the names of functions. | session6.py | Passed |