Is potentially a valid credit card number. Luhn algorithm is a set of instructions for checking whether a number For example,Īll Visa cards must start with the number 4)Īn algorithm is a set of instructions for accomplishing a specific task, so the (In practice there are also additional restrictions. That a number is valid if it passes the Luhn algorithm. What makes a credit card number valid? For our purposes, we'll assert #Background Information - Valid credit card numbers This must be completed before leaving the lab.Īfter that you should start working on Part 2.
#Algorthm for a credit card validator code#
We will double check your code and your test cases, ask you a few questionsĪnswer any questions you have, and award your points for Part 1. good use of horizontal and vertical white space Please enter a positive integer in the range 100-999:īefore finding a TA or professor, make sure your functions have Instead, you should just convince yourself that your `main` **Note:** since main functions don't take arguments and always return `None`, weĬan't programmatically test them for correctness the way we test otherįunctions. Input from the user, you should immediately convert it to an integer. Remember to add a docstring for your main function! Implement the `main` function in `creditcard_part1.py`, which shouldĪsk the user for a positive integer between 100 and 999 (inclusive) Line with a set of assert statements that thoroughly test your `sum_digits`įunction, and convince yourself that your implementation is correct. This will always throw an error! Replace this Note that for `sum_digits`, the tester file only includes one assert `decimal_right_shift` as helper functions! Remember to add a docstring for Hint: you will want to use the functions `last_digit` and You may assume that the value passed as anĪrgument to sum_digits is always a positive 3-digit integer. `sum_digits`, which takes a 3-digit integer as a parameter and returns the This time it should pass the second batch of tests! When you believe your function is working correctly, re-run the file `decimal_right_shift(1)` should evaluate to `0`. `decimal_right_shift(123)` should evaluate to `12` and `decimal_right_shift`, which takes an integer and returns the integerĬonstructed by removing the last digit. Go back to the file `creditcard_part1.py` and implement the function
Implementation of `last_digit` passed all of our tests and should be correct! `creditcard_tester.py` if it prints `last_digit passed`, then your Programatically test our functions! Try running the file
`False`, the `assert` statement throws an error. Statement evaluates a boolean expression if that expression evaluates to `creditcard_tester.py` contains a bunch of `assert` statements. You should see at the top that this file importsįunctions from the other two files. When you believe your function is working correctly, open the file Returns the last digit of that integer (as an int). Implement the helper function `last_digit` which takes a positive integer and Copy all three files into the (recently created) That contains three files (`creditcard_part1.py`, `creditcard.py`, and
#Algorthm for a credit card validator download#
Then download the (cc.zip), and unzip the file (on a Mac, The right place, or you will likely have trouble finding your files later.* *Double check that you are creating the project in | 2 (lab/home) | (#submission) |Ĭreate a new project named `CreditCards` in the `CSCI051p-Workspace` youĬreated on your Desktop. Of parameter types and return a variety of types. For this assignment, you will implement functions that take a variety Including testing functions and modeling function call behavior with stackįrames. This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development.The goal of this assignment is to give you more practice with functions, Hopefully, that should help you locate which part of that code has a problem, and what the problem is. Did it do what you expect? If so, move on to the next line. Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to). When it reaches the breakpoint, the debugger will stop, and hand control over to you. Put a breakpoint on the first line of the method, and run your app. Once you have an idea what might be going wrong, start using the debugger to find out why.
0 kommentar(er)
