14TH Weekly workload and progress statistics

14TH Weekly workload and progress statistics

This week's PSP:

C (category)	C (content)	s (start time)	st (end time)	i (Interrupt Time)	t (actual time)
Activities	This week's meeting	14:00	15:00	10 minutes	50 minutes
Write a blog	Testing and Publishing	20:00	22:56	30 minutes	146 minutes

Pie chart:

This week's progress:

Essays cumulative number of words	535+2690+538+1717=5499
Code cumulative number of lines	The number is not clear
Key points of knowledge	Stability and release phase, coded UI test and review software testing

Essay words and lines of code line chart:

This week is summarized as follows:

The 14th Chapter software test

I. Test design method Classification: Black box and white box

1. Black box: is a behavioral test design, that is, from the behavior of the software, rather than from the internal structure of the design test, unable to understand or use the system's internal structure and knowledge.

2. White Box: Designers can see the internal structure of the system and use the internal structure and knowledge to select test data and specific test methods.

Second, the purpose of testing classification: unit testing, functional testing, integration/scene/System testing, pressure testing

Iii. Test timing and job classification: Smoke test, regression test

Iv. documentation in the test work

1. Test plan, test master

2. Test Design Manual (TDS)

3. Testing cases (test case)

4. Program Error Reporting (BUG report)

5. Testing reports (test report)

Chapter 15th stability and release phase

Version: Alpha, ZBB, RC, RTM, RTW (RTO)

First, tricks:

1. Design Changes (DCR)

2.ZBB (Zero Bug Bounce): ZBB (Handling 48-hour report defect), Bounce (Bounce), damping (the rebound amplitude becomes smaller)

3. Final regression test

4. Cut off the function

5. The threshold for fixing bugs is gradually increasing

6. Gradual freezing

Ii. progressive release of different frequencies and non-coverage areas

Iii. Post-Hindsight conference

IV. Vision and Objectives: what have we learned and what improvements will be made?

1. Planning

2. Resources

3. Change Management

4. Design/Implementation

5. Test/Release

Five, how to open a postmortem meeting:

1. Meeting Atmosphere, environment

2. Speak freely

3. Not to the people

4. Reference template, in-depth study

5. Statements

6. Minutes of meetings, comments on improvements

7. Voting

8. Implementation of the improvement comments

On-Machine operation: Coded UI test

First, automated testing

Automated testing refers to the automation of software testing, which is to run the system or application under preset conditions, evaluate the results of the operation, and pre-conditions should include the normal bar

components and abnormal conditions.

Automated testing is the process of translating a man-driven test behavior into a machine execution. Typically, after a test case has been designed and reviewed, the tester

According to the procedures described in the test cases, the results are compared with the expected results. In this process, in order to save manpower, time, or hardware resources,

The concept of automated testing is introduced to improve test efficiency.

VS2010 coded UI tests, which are part of an automated test, test that the application's user interface is functioning properly. Coded UI tests for the application process

User interface control, and verify that the correct control is displayed with the correct value.

A simple example

A New Test Project

1. First open VS2010, select Test--New test

2. Select the coded UI test, CV a UI test, named CodedUITest1.cs

3. Once created, we can see that the directory structure of the project is as follows

Two Recording programs and playing back

1. An existing program

2. Now we can start recording and record the test content as the actual operation

3. After clicking OK, you can see a UI Test builder pop up in the bottom right corner of the screen, and then you can do it after clicking Record.

4. Then first enter the wrong user name and password, then click Login, then pop-up prompt "User name and password error"

5. At this time we can click on the record panel to pause the recording, then click "Generate Code", and put the previous action into the method inputerroruidpwd

6. Click the crosshair on the recording panel at this time (this time the crosshair has been enable), and hold down the mouse, drag the mouse over the text just above the pop-up box and then release, and then test the Generator Object Library window will automatically pop up, VS2010 will capture the label object on the popup box as shown in:

7. Now we are going to do the first verification, is to verify that the popup "user name or password error!" "Whether it bounces out, if it is, then the test passes, if not, then fails, then the previous step Illinois, first to confirm that the left list in the" UI user name or password error Text "Object is selected, and then select the Exists property in the list on the right (this property indicates whether the label exists, Exists is true, does not exist, or false), click Add Assertion

8. Then pop up the window to add the assertion for exists, here we need to select AreEqual, the comparison value is true, indicating that we assert "user name or password error" This label exists, if the test is run when the label does exist, the test step is passed, otherwise it is a failure

9. Then click on the Generate code for the recording panel to generate a method for the assertion you just added Asserterrorwindow ()

10. Then we continue to start recording, after the recording is turned on, first click on the "User name or password error" Pop-up box, and then use the same method as described above, enter the correct user name and password, to determine whether the popup is "login Success", add Inputrightuidpwd () Action method and Assertrightwinow () assertion method, which can be recorded at the end

11. Then we can click to run to test

12. VS2010 will then automatically operate the login window of the program you just demonstrated and report the test results

14TH Weekly workload and progress statistics