A few months ago I posted Atomic clock + alarm challenge. Daniel took the challenge and submitted a solution. I like it! His approach uses a timer object. (Great minds think alike.) The command line use of remindme_atom is simple, and the modal pop-up dialog is effective. I also got a kick out of his sound stream when my alarm went off. Nice touch!
Did you really think I'd stop there? Now that we have a solution to the previous challenge, the new challenge is to brainstorm a test plan for it. You might start by understanding different ways remindme_atom was intended to be used. How do you make sure it does exactly what it is supposed to do? How many test cases can you think up? How could you accidentally misuse it. Which cases are not worth testing? What steps would you take? Do any other considerations come to mind?
Don't jump in head first. Rather, let's talk about how you test code that you write, or M-files from others that you rely on. You do test your own code, somehow, right? Please share your thoughts here.
댓글을 남기려면 링크 를 클릭하여 MathWorks 계정에 로그인하거나 계정을 새로 만드십시오.