Customized testing of software testing

has been engaged in software testing work for 5 years, think about it, have never heard of a test called a customer test. Seemingly unfamiliar nouns, in fact, not so unfamiliar, do not believe, first look at the concept of customer testing:
The so-called customer testing, is a software product customization capabilities of the test, it is focused on simulating the user's use of the product scene , through the product's public documents, tutorials and product development interface to use, according to the product service department to provide customer needs, to develop the corresponding functional sample, and write the corresponding documents for the customer to learn and reference.

After reading the concept, can not help but sigh, oh, this is the scene test Ah, scene testing for testers should not be unfamiliar, but, the customer test is really equivalent to the scene test? With this problem, we continue to read.

Since the name is called a custom test, then, as a tester we can first determine that, at this moment, I am a real customer, or, indeed, a real customer. How does a customer treat a purchased product? You can recall the circumstances of your purchase, in general, for the newly purchased items, we will first read the documentation, of course, not everyone does so, this situation is now excluded.

Generally speaking, a software product provided to the customer in addition to the compiled, packaged installation materials, is the documentation. As customers of software products, if they want to do custom development based on the software product, they must have a comprehensive and in-depth understanding of the software by means of documentation, especially in terms of development interfaces (APIs). Therefore, in order to better play the customer, the test engineer of the customer-based test team must be the same as the customer, only from the documentation to obtain the various information needed for development. That is, they cannot read the development design document and the real implementation code.

The problem is that some of the project's documentation is not written the first time, so what if you need to do a custom test of a feature?

In fact, although at the beginning of each development cycle we do not see the complete documentation, but there will always be some draft of the relevant documents exist, although incomplete, may even be overturned or canceled, but a day early to understand what customers can get, more than one day to do the design of customer testing.

In general, the customer test is allowed to view the requirements analysis document because, since it is a mock customer, the customer's needs are clearly what the customer-testing staff should know. There is also the solution specification and functional testing of the design document, the former is on the basis of customer requirements and related functional description, risk, prioritization and other content, the latter description of the features will certainly be written to the customer's documentation. And what we call a customer's documentation is generally the responsibility of a dedicated document writer.

Customer-tested Software design process:

In general, the customer test consists of 4 phases:

Identified in the research requirements phase
Design phase
Implementation and testing phase
Documentation and tutorial Validation

All customized scenarios that need to be tested need to be negotiated with the software Services Department to ensure that the customer needs the most.

To better play the customer, we should have a good understanding of the customer's industry. So the client-based testers need to be clear at the outset what the customer's needs are from the characteristics of the product, and as such customers, what goals will be raised when customizing the features of these products.

Identify the stage of research requirements: this requires that we need to be in the early stages of the intervention test, although it may not be possible to get a complete documentation, but we can get to the design stage of the customized test as early as possible through the drafts and requirements documentation for the relevant documents.
Design phase: As the name implies, is the design of the test.
Implementation and testing phase: This section contains the process of the developer's implementation of the product and the formal involvement of the customer in the test.
Documentation and tutorial Validation: Because the documentation and the product are delivered to the customer at the same time, it is inevitable that the documentation and tutorials should be tested accordingly.

Through the above description, although not so detailed, but we can already answer the question of the beginning of the article, the customer test is equal to the scene test? The answer is not equal, but contains the scene test, because we need to simulate the customer's use of the product in any possible circumstances, whether it can be used properly and whether it will have a corresponding impact on the product itself is the most important focus of customer testing. At the same time, the documentation and tutorials need to be tested accordingly.

So, for a customized test, perhaps we can list one of the following formulas:
Customized test = scene Test + functional Test + performance Test + regression Test + documentation test

Test the pit is very deep, we need to explore, customer-based testing, well, it seems that there are few articles on the internet, just see, just casually chat.

Customized testing of software testing