Software Test-7 Some ideas in the actual test

Objective

It has been a few weeks since we learned software tests. Theory has learned a lot, but actually doing it yourself is a two-time, very simple experiment. Although only two simple experiments, but, two experiments to my harvest is very big, let me have a lot of my own ideas of software testing.

A very large amount of work

The amount of work that is spent on software testing is really a big gap compared to what I imagined. I have been very dismissive of software testing this link, I think this link is dispensable. In fact, after I've completed a program, or completed a project, I don't spend a lot of time testing it systematically. I feel that I have passed the self-test when I write the code, and that the completed program should not have any serious bugs. Even if I want to test this program, it should be a relatively simple thing, a little more time is enough. " isn't it just a little bit of testing ?" "That was the thought.

In fact, when I was doing the tests, I spent more time on software testing than I did writing code. For example, before doing unit tests, I wrote a sorting algorithm that took only 5 minutes, up to a maximum of ten minutes. To complete the unit test, I need to draw a flowchart, turn it into a graph, then find a valid path and design the test case, and finally test the results. I didn't pay attention to how much time it took, but at least half an hour or more. Of course, I test the function is designed to the function of the algorithm, such a function unit is of course more complex, the general function should be much simpler than this, and spend a lot less time. But the amount of work it spends is still huge .

Of course, in order to reduce the workload of software testing, there are now a lot of testing tools and testing framework can be used for us, we must also learn how to better use these tools to simplify the work of software testing , improve the efficiency of software testing. Our use of Visual Studio can help us to complete software testing faster and better, greatly improving the efficiency of software testing.

People are smarter than machines.

In order to improve the efficiency of software testing, we must rely on some software testing tools. But sometimes we don't believe in machines too much, and people are always smarter than machines.

This is one thing I found when I was doing a UI test:

Premise: use Visual Studio to do automated testing , the following software to encode the UI test;

No problem has been tested, each button can be entered normally, or return normally.

But I was in the mood to do a bit of AD Hoc test, according to their own ideas casually point, try to change the screen resolution, as follows:

The screen changed from 1280x768 to 1920x1080, image button warp verification, software not working properly.

This is the way to use the tool, only to find the errors you expect, some strange mistakes are likely to be found, so the machine can not completely replace the human.

Iii. Summary

Software testing this discipline, or the technology, is very important in both theory and practice. Only the perfect theory, in order to let us faster and better software testing, there is no theory to guide us to test, software testing is very difficult, it is likely to spend a lot of time but not to find the corresponding bug. And practice, can really let us out of the theory, really learn how to test software, to most effectively test the problem of software.

Software Test-7 Some ideas in the actual test