Coded UI test Project--visual Studio 2013

In a previous experiment, the experimental content is a UI test that encodes a Windows Store app , with detailed instructions for the experiment steps:

1. Create a new Coded UI test project for Windows Store apps, select the visual c##→ store app → Coded UI test project (Windows).

2. Choose to edit the UI map using the Crosshair tool, and then the coded UI Test Builder toolbar appears.

3. Use the Crosshair tool in the coded UI Test Builder to select the app tile, right-click AutomationId, and select Copy value to Clipboard. Use the values in the Clipboard later to write an action to launch the app that you can test.

4. Run the application and add the application control with the Crosshair tool (shortcut: ctrl+shift+i).

5. Then similar to step 1.4, select all types of controls in the application.

6. Select the Generate Code button in the Coded UI Test Builder toolbar and choose Build to create code for changes to the UI control diagram.

7. Close the coded UI Test Builder toolbar, the VS2013 main interface appears, open uimap.uitest to find all the control information you added earlier.

8. Modify the code, for example, to add the control to the code.

9, click test → run → all tests, you can conduct test analysis.

10. After the test is complete, the test explorer will show that the test was passed and the run time is 9 seconds. At this point, the experiment is complete.

I've done a coded UI test for a non-Windows Store app before, and this time I tested the Windows Store app, but there are a lot of different things, like a UI test that encodes a non-Windows Store app that can be recorded, The process of testing can be visually observed when you run the test, and testing the Windows Store app without recording the process will initially make me feel like a start. Then by looking for information and ask classmates, I am gradually familiar with this process, but also have their own understanding. The reason why you chose to test this application (LOL Tank hero Introduction) is because it is a relatively simple application, does not contain information of the input process, is more suitable for just beginning to contact the software test we use to practice.

Coded UI test Project--visual Studio 2013