Black Box 编程设计写作

” Black Box 编程设计写作2021/7/6 HW1: Writing Black Box Tests1/6 HW1: Writing Black Box TestsDue Tuesday by 11:59pm Points 15MotivationThis week we took an in depth look at our first testing technique: black box testing. Oneof the key elements of black box testing is that the tester does not have access to the source. Inthis assignment, you will be given a specification and list of requirements. This will give youexperience writing unit tests in a Black box testing scenario.Course Learning Outcome(s):Apply testing techniques, including black-box And white-box techniques, automatic testingactivities, and regression testing (CLO 4)Module Learning Outcome(s):Apply black box testing techniquesDescriptionFor this assignment, you will be writing unit tests based on the followingspecifications/requirements.You will write a series of unit tests to test a function called credit_card_validator (written for you)that is passed a sequence of digits as a string that represents a credit card number. This functionwill return True if it is a valid credit card number, otherwise, it will return False .Depending on the credit card issuer, the length of a credit card number can range between 10 and19 digits. The first few digits of the number are the issuer prefix. Each credit card issuer has anassigned range of numbers. For example, only Visa credit card numbers may begin with 4 , whileAmerican Express card numbers must begin with either a 34 or 37 . Sometimes, credit cardproviders are assigned multiple ranges. For example, MasterCard card numbers must start with thenumbers between 51 through 55 or 2221 through 2720 (inclusive).The last digit of the number is referred to as the check digit and acts as a checksum. Most creditcards calculate this check Digit using the Luhn algorithm (see resources below for how this iscalculated).In order to limit the scope of this assignment, we are going to limit the number of credit card issuersto 3: Visa, MasterCard, and American Express. Each has its own prefixes and length requirements.VisaPrefix(es): 4?2021/7/6 HW1: Writing Black Box Tests2/6Length: 16MasterCardPrefix(es): 51 through 55 and 2221 through 2720Length: 16American ExpressPrefix(es): 34 and 37Length: 15Your task is to create a series of tests that attempt to reveal bugs in the implementation. As this isblack box testing, you will not have access to the source so you must use what you have learnedthis week to generate test cases.You will be submitting your code to Gradescope which will auto grade your tests. In order to get fullcredit on the assignment, you will need to locate all 6 bugs in the code (refer to the rubric for fulldetails). Some are easier than others. Bug 5 is easy to miss without using Partition Testing and Bug6 requires using what you know about common errors to design your tests.You are free to determine how you generate your test cases. You may do it completely manually, oruse an automated tool like the TSLgenerator. No matter how you generate your test cases, in yourfile testing file ( tests.py ), you need to include a comment for each test case describing:What the test case (i.e. credit card number) is meant to verifyHow you determined what to Use as the test caseHere is an example:# Verifies if Master Cards with valid lengths and invalid check bits returns False# Picked using Category Partition Testingdef test11(self):self.assertFalse(credit_card_validator(….))You also need to ensure you have test cases that do a good job covering the input domain. Thismeans that at the very least, you need to have a test case for each of the prefix ranges listedabove.Please submit all your tests, even the ones that do not find bugs. Remember, you are practicingwriting a testing suite, which can be used to test the code again if changes are made. There maybe a situation where a previously passing test fails when someone updates credit_card_validator .Finally, your test suite needs to be free of linting errors using the PEP8 standard; this will beimportant later when working on shared repositories. If you are unfamiliar with linting, please seethe resources below. The easiest way to accomplish this is to ensure that there are no squigglylines under your code in PyCharm (You will need to change PyCharms default line length to 79 tomatch PEP8). You can also use the PEP8 Online tool below to copy and paste your code to verify ithas no errors.Restrictions ?2021/7/6 HW1: Writing Black Box Tests3/6For this assignment, you are prohibited from using Random Testing. Yes, Random Testing is a typeof Black Box Testing, but you will be working with this approach in a later module (Exploration:Random Testing). You will not Receive points for any bugs triggered by Random Testing. Thismeans that you cannot use code to generate the test cases, you need to come up with themyourself. Please restrict yourself to using other Black Box Testing techniques: Error Guessing,Partition Testing, and Boundary Value Testing.Hints You will need to includeif __name__ == __main__:unittest.main()It is best to only have a single assert in any test. Once one fails, the rest of the code in the testisnt executed.You may assume only strings of digits are being sent to credit_card_validatorI used the TSLgenerator to create roughly 35 test cases and then picked some to breakUse what you learned about Error Guessing and Boundary Values to find tricky bugsYou will need to use from credit_card_validator import credit_card_validator in your tests.pyTo ensure your tests are correctly importing the function for testing, you may put the followingdummy code into a file called credit_card_validator.pydef credit_card_validator(num):passYou may submit as many times as you want to Gradescope to check how well your test suiteperformsWhat to turn inSubmit to Gradescope your testing suite; it must be named tests.pyThis file will include at the top of each test a comment describing your test generationmethodologyThis file will contain tests that cover all prefix rangesThis file will be free of PEP8 linting errorsDont remove passing tests, submit them allResourcesLuhn algorithm ( httpss://en.wikipedia.org/wiki/Luhn_algorithm)Generate Credit Card Numbers ( httpss://bestccgen.com/)Luhn Number Checksum (useful when generating valid check digits)( httpss://www.dcode.fr/luhn-algorithm)PEP8 Style Guide ( httpss://www.python.org/dev/peps/pep-0008/)PEP8 Online (copy and Paste your code to check) ( https://pep8online.com/) ?2021/7/6 HW1: Writing Black Box Tests4/6Black Box TestingLinting Python in VS Code (use flake8) ( httpss://code.visualstudio.com/docs/python/linting) ?2021/7/6 HW1: Writing Black Box Tests5/6 Total Points: 15Criteria Ratings PtsBug 1 Found 2 pts Full Marks 0 pts No Marks Bug 2 Found 2 pts Full Marks 0 pts No Marks Bug 3 Found 2 pts Full Marks 0 pts No Marks Bug 4 Found 2 pts Full Marks 0 pts No Marks Bug 5 Found 2 pts Full Marks 0 pts No Marks Bug 6 Found 2 pts Full Marks 0 pts No Marks Test Case Methodology Contains a comment for each test case with: * What it is meant to verify * How it was selected 1 pts Full Marks There is a comment for each test case describing: * What itverifies * How it was selected 0.5 pts Half Marks At least half of the test cases contain comments that describe: * What itverifies * How it was selected 0 pts No Marks More than half the test cases are missing comments that describe: * What it verifies * How itwas selected Contains tests for each Prefix range Contains tests for each prefix range (4, 34, 37, 51-55, and 2221-2720) 1 pts Full Marks All 5 ranges covered 0.5 pts Half Marks At least 3/5 ranges covered 0 pts No Marks Fewer than 3 ranges covered tests.py is free oflinting errors tests.py is free oflinting errors 1 pts Full Marks There are no linting errors 0.5 pts Half Marks There are no more than 2linting errors 0 pts No Marks There are 3 or morelinting errors ?请加QQ：99515681 或邮箱：99515681@qq.com WX：codehelp

“