Chinatest Web Service Testing Tool summary on the first day

I am lucky to have won the first prize in the Weibo lottery. I won the first prize in my life and won the tickets for the China Software Testing Conference (chinatest) 7 and 8.

 

On the first day of the meeting, there were a lot of content, except for the main venue in the morning, there were many sub-venues in the afternoon, you can only choose to listen to interest, a total of four sessions in a day

 

1. Martin Pol -- evolving towards service driven Test Management

Service-oriented test management. I personally do not agree with the service-oriented test team, mainly concerning the right to speak. I have established a service-oriented test team in my career experience,

In the communication with the development, the loss is not small. Because of the positioning service, there is a lot of resistance in the testing process to promote development, and the development has a low degree of attention to quality, the status of the test team eventually shrinks.

In the question stage, I asked the Team's KPI assessment, which is also a question generated by servitization. Since it is a service type, there will be a customer satisfaction evaluation, and a development team will be among the customers.

Of course, my professional experience has always been in the Internet field. The traditional testing organization has created many service-oriented teams and should be widely used in the financial and telecom field.

2. Richard Bender -- how do you know when you are done testing?

When to end the test; Richard provides a lot of criteria to determine when the test can be performed, from the black box to the white box. At the same time, he focuses on the path test in the black box test and the white box test, which shows a deep

I also reviewed these two testing methods.

However, in the Internet field, due to the characteristics of continuous release, unlike the one-time delivery of traditional software, the criteria for determining when the test ends will change. I think it can be extended

How do you know when you can release the product?

In Google's search products, the frequency of release on a Monday is basically achieved. To achieve such a short release, in addition to continuous integration, another simple criterion is that this version has no bug of P0/P1.

 

3. Yan Xiaomei -- Test Design Problems Investigation

Problems encountered in the test design. The instructor, taking his personal experience in Huawei as an example, proposed various problems encountered in the test design,

I did not mention how to solve these problems in this speech. However, instructor Yi has summarized the solution mqtcs and promoted it to model the independent "component" in the tested system,

Test requirements are formed based on requirements. test specifications are obtained from test requirements, and corresponding test cases are formed. A large number of conventional test methods are required in design cases,

Therefore, basic testing skills are indispensable.

Another question is how to evaluate the effectiveness of the test, Mr Yan's blog has two blogs that discuss this very well, http://www.taixiaomei.com/archives/date/2012/07
In the solution mentioned above, we mainly look at component as a black box. Can we take it further and learn about development and design in advance? An example mentioned in the speech is used in development

If... else or switch is uncontrollable, but in Google, every changlist product member submitted by the developer can see it. This can also be used as an input to the test design.

 

4. Cheng Yanbin-integration test of SOA Development

Integration Testing of the SOA architecture; now many teams will use the SOA architecture, and there will be many services on the backend, each service is not independent, there will be a lot of interaction, if only through the GUI for testing,

Troubleshooting is difficult or time-consuming, so we can test the service to push forward the test. After the service development is complete, we will intervene in the test and use virtualization or faked data to complete the test.

Early verification means that functional testing, service testing, and performance testing (divided into service and GUI) at the front end can form a complete system. tests can be completed well using Rational tools.

However, the service test may also encounter the following problems:

A. when there are a large number of services, the workload will increase. At the same time, maintenance is also a problem due to schema changes, especially when added to continuous integration, frequent failures will lead to frequent repairs, there must be a trade-off,

Such as service selection, which services need to be tested, and development engagement

B. Public/private service. We know that basically all Web services are public. It is very convenient to use tools such as rational for data-driven testing, but private such as WCF in my experience.

I don't have any testing tools. I want to join the unit test and the independent testing tools developed by the Team (I have discussed Web Service Testing Tool summary)

The above are some of my personal feelings after the meeting. You are welcome to exchange ideas.

 

PS:

Chinatest, http://www.chinatest-conf.com/index.aspx

Chinatest, our test!

 

We love test ),

We have passion (enthusiasm ),

We advocate sharing ),

We are pursuing a high level )!