question archive taking the 030108 course at the University of Toronto Copying for purposes other than this use is expressly prohibited All forms of distribution of this code , whether as given or with any changes , are expressly prohibited All of the files provided for this exercise are: Copyright (c) 2028 Mario Badr, Jennifer Campbell , Tom Fairgrieve , Paul Gries, and Jacqueline Smith Complete the following steps (1) In addition to this file , download and open fluffy_functions
taking the 030108 course at the University of Toronto Copying for purposes other than this use is expressly prohibited All forms of distribution of this code , whether as given or with any changes , are expressly prohibited All of the files provided for this exercise are: Copyright (c) 2028 Mario Badr, Jennifer Campbell , Tom Fairgrieve , Paul Gries, and Jacqueline Smith Complete the following steps (1) In addition to this file , download and open fluffy_functions
Subject:Computer SciencePrice: Bought3
taking the 030108 course at the University of Toronto Copying for purposes other than this use is expressly prohibited All forms of distribution of this code , whether as given or with any changes , are expressly prohibited All of the files provided for this exercise are: Copyright (c) 2028 Mario Badr, Jennifer Campbell , Tom Fairgrieve , Paul Gries, and Jacqueline Smith Complete the following steps (1) In addition to this file , download and open fluffy_functions.py in Wingiei (2) Review the test cases you chose for the all_fluffy function as part of the Choosing Test Cases exercise in the week 9 Rehearse llecture . (3) Implement the test cases you chose as test methods in the TestAllFluffy class below Make sure you save your file regularly (4) Run your tests on the correct version of all_fluffy from the fluffy_functions.py file . We have provided an import statement below to help you do that. Make sure your tests all run and pass on the correct code. (5) Run your tests on the buggy versions of all_fluffy from the fluffy_functions.py file . The simplest way to do that is to temporarily rename the buggy functions to all_fluffy one at a time. At least one of your tests should fail on each of the buggy versions of the function (6) When convinced that your tests are complete , submit your modified file to MarkUs . You can find instructions on submitting a file to MarkUs in the Week *2* Perform on PCRS. (7) Verify you have submit the right file to MarkUs by downloading it again and checking it is the one you meant to submit (8) We have also provided a checker test for you to run in MarkUs . This week the checker runs your tests on a correct version of the all_fluffy function We will not be marking your style on this exercise , so there will be no PyTA check We will run additional tests with different versions of buggy code when we mark your submission import unittest from fluffy_functions import all_fluffy # Do not change this import statement class TestAllFluffy (unittest.TestCase ): def test_empty_string (self) -> None : """Test that the empty string is fluffy .""" expected = True actual = all_fluffy (") msg = "Expected {}_. but returned {}".format (expected , actual ) self.assertEqual (actual , expected , msg) # Add your other test methods here
