Privacy Statement. Continue Cancel. Free Trial. Tutorial Microsoft Visual C for beginners. See System Requirements. Available on HoloLens. Description A practical guide to developing Windows Forms Desktop. Show More. People also like. Control Center 3. Microsoft Maquette Free. Additional information Published by NKsoft. Published by NKsoft. This browser is no longer supported.
Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No.
Any additional feedback? Open Visual Studio. Open Visual Studio, and on the start window, choose Create a new project. Note If you don't see the Blank App Universal Windows project template, click the Install more tools and features link. Choose Toolbox to open the Toolbox fly-out window. Click the Pin icon to dock the Toolbox window. Click the Button control and then drag it onto the design canvas.
Select the Pin icon to dock the Toolbox window. Select the Button control and then drag it onto the design canvas. Double-click the button control on the design canvas. Edit the event handler code in MainPage. Here is where things get interesting. SpeechSynthesizer ; Windows. SetSource stream, stream. ContentType ; mediaElement. The app should look similar to this: Click the Hello World button.
You can call these other classes and methods from your test methods. In this procedure, you'll write unit test methods to verify the behavior of the Debit method of the BankAccount class. You can delete the default TestMethod1 method, because you won't use it in this walkthrough. The first test verifies that a valid amount that is, one that is less than the account balance and greater than zero withdraws the correct amount from the account. Add the following method to that BankAccountTests class:.
The method is straightforward: it sets up a new BankAccount object with a beginning balance and then withdraws a valid amount. It uses the Assert. AreEqual method to verify that the ending balance is as expected. Methods such as Assert. AreEqual , Assert. IsTrue , and others are frequently used in unit testing. For more conceptual information on writing a unit test, see Write your tests.
While the test is running, the status bar at the top of the Test Explorer window is animated. At the end of the test run, the bar turns green if all the test methods pass, or red if any of the tests fail.
Select the method in Test Explorer to view the details at the bottom of the window. The test result contains a message that describes the failure. For the AreEqual method, the message displays what was expected and what was actually received. You expected the balance to decrease, but instead it increased by the amount of the withdrawal. The unit test has uncovered a bug: the amount of the withdrawal is added to the account balance when it should be subtracted.
This section describes how an iterative process of analysis, unit test development, and refactoring can help you make your production code more robust and effective.
You've created a test method to confirm that a valid amount is correctly deducted in the Debit method. Use the ThrowsException method to assert that the correct exception has been thrown. If you temporarily modify the method under test to throw a more generic ApplicationException when the debit amount is less than zero, the test behaves correctly—that is, it fails.
The method being tested can be improved further. It would be better if we could tell which condition in BankAccount. Look at the method being tested BankAccount. Debit again, and notice that both conditional statements use an ArgumentOutOfRangeException constructor that just takes name of the argument as a parameter:.
There is a constructor you can use that reports far richer information: ArgumentOutOfRangeException String, Object, String includes the name of the argument, the argument value, and a user-defined message. You can refactor the method under test to use this constructor. Even better, you can use publicly available type members to specify the errors. First, define two constants for the error messages at class scope. Put these in the class under test, BankAccount :. Refactor the test methods by removing the call to Assert.
The Microsoft. Contains method provides the ability to compare two strings. Currently, the test method doesn't handle all the cases that it should.
0コメント