Problems and workarounds encountered in the Software testing UI test

April 10, 2014, the first time on the machine class, the Win8 app application to the black box test, but after watching the video tutorial in the actual operation, but encountered a lot of difficulties. The following will be their own problems and solutions to share with you, hoping to get more advice and experience.

"Issue 1" record button is grayed out and cannot be used

(1) New project, file---->windows App Store-coded UI Project test (Windows Store app)

(2) Click Confirm in the Pop-up dialog box

(3) successful UIMap, but the recording key is gray

I believe many classmates and I like the distress, how to do? Most students choose to try another route.

"Question 2" try the "test-and-coded UI test project"?

(1) Coded UI Project test----new project----------

(2) Click OK in the Pop-up dialog box, and the UIMap appears.

Here, important to see the Red record button ~ ~ Good fun ~ ~ But the difficulties encountered later told me, this time proud is too early!

(3) Open "E Clock"

E Colck is a win8 App, with world time, stopwatch, countdown function, support simple interface color switch.

(4) Click the Red Record button to record the "Replace color" action

(5) Click the Generate Code button when recording is complete and name "ChangeColor"

(6) According to the above operation to change the time zone, Countdown, stopwatch and other functions to record, observed. CS in the following code to survive

(7) test run-all tests, run-to-test, complete

Here, I almost thought the test was really successful, but ... Here's the question.

(8) Click UIMap in Solution Explorer to view

The following hints are found, and each function has the same hint. Well, it turns out that vs did not successfully test the program t_t

"Solve 3" to use Simulator!

Under the guidance of the great God, we must finally embark on a bright road.

(1) Run "program Files (x86) \common Files\Microsoft Shared\windows simulator\11.0" Microsoft.Windows.Simulator.exe in the folder, start the emulator

(2) Open the program you want to test in the simulator

(3) The process of recording and generating code in the middle is consistent with the above

(4) test run-all tests, run-to-test, complete

It is necessary to note that the test run may be slow, but do not minimize the emulator window, otherwise it may not pass the test. Because clicking, entering, and so on cannot be done in the hidden window.

(5) Open Uimap.uitest again

It's a success to test here ~ ~

"description" The application case selected above is not the case I used to end up with, because basically only click, no keyboard input, bad design test case.

Problems and workarounds encountered in the Software testing UI test