Test tour of "Bean Paste"

A qualified software must be strictly tested before going online.

The previous courses were rarely involved in testing. You may not have any idea about how to perform rational and scientific tests.

In this blog, let's talk about some of our own simple ideas.

1. Code Review

No one is a god.CodeThere are a lot of bugs, and it is difficult to find them. This requires code review. The code you write is difficult to find errors. At this time, let another person take a look at it and often find problems quickly. These problems are usually very small errors, but they are fatal.

2. Unit Test

Unit testing is the minimum level of testing activities to be carried out during software development. During unit testing activities, the independent units of the software areProgramIn the case of isolation. For example, if one of our functions is to convert the representation of a certain time to another representation, we must ensure that the correct output is generated under any reasonable input.

3. Interface Testing

Before development, we divide the entire software into several modules. Different students have different modules and communicate with each other through interfaces, this requires that the communication between the two modules is accurate, so that different modules can be bonded together and work together. For example, after you click an item in the search list, you should jump to the detail page of the corresponding item. The parameter passed is ID and the type is string.

4. Functional Testing

We must ensure that we can implement the features we promised. This is a basic requirement for users. In this regard, we can test it on our own. When it's okay, let's have a try and see if there will be any problems.

5. Handling exceptions

Software does not always run as expected. It will always encounter various exceptions and we need to be able to handle them. For example, what if a network exception occurs? Users cannot be fooled, so they should be prompted that there is a problem with the user's network, rather than a problem with bean paste.

6. Usability Testing (interaction)

Our software needs to be simple and easy to use, and users do not need to take instructions to learn how to use it. The ideal situation is that our design conforms to the user's usage habits. It is very easy for users to use our software. Therefore, the more features we use, the better, software that is easy to use and can solve user problems is what users need. In this regard, we need to find real users to see how they use our software for the first time and whether they can complete their tasks smoothly.

7. Stress Testing

We don't need this because we don't have our own Sever. We can retrieve data directly from the Douban API.