Seeing this topic, many people engaged in testing work will be very surprised. Is there a fun (opening international joke, throwing eggs to this blocked guy), everyone will finish the article first, don't lose eggs.
I have been graduating for three months, and I have been in contact with the test work. In the six months of testing work, I have tested for testing, especially when I started to contact the test, just think Complete the test as soon as possible, thinking about what runs in the program, I haven't run yet, then I repeat the case of the boring case, and I spend time thinking about how I should take a test process, how do I test? Efficiency is improved, even interested in testing. When I gradually be familiar with the test work, especially the official graduated back to the company, I realized that most of the testers were painful: Test is indeed boring. When you have a case written by yourself or others to do the first time to perform the case, you have a boring feeling, let alone you have to repeat the NT times (is learning mathematics, I believe everyone I know that the meaning of N), such a day will gradually disintegrate a tester's enthusiasm for his work, and even make him hate this work and finally leave this work. Why do you like this, because he feels that his work has not fun, and the repetitive work is the most fundamental reason. We can get rid of this boring situation (not working), develop work, my answer is the introduction of automation tests (maybe everyone has a better way, welcome to inform me).
About automated tests, everyone can search for a lot of pile through Google (where there is a pile of well-known than my understanding), I have to talk about my actual experience. The introduction of automated tests is a step-by-step process. It is not implemented immediately by purchasing a large number of devices and software (of course, it will be easier for equipment and software implementation), but we use us in actual test work. The brain (the human brain has no computer to obey, but it is smart, haha), how to use our brain, of course, not to use our brain to perform test cases, we need to use our brain to think about how we improve the test process, which Part can be automated (all tests can be automated to be completely falundated before artificial intelligence is not mature), and then of course it is implemented. I just said that we can't do a complete automation test, and I also want to emphasize the automation test is a step-by-step process. Like software development, we have automated many small parts of the test process, and then you can associate them together. To a piece.
The introduction of the automated testing process and improvements may have some difficulty. It requires some scripts and programming options. It is some fun to make the test change (especially those who like challenging work), even if we It is very poor in the bottom, and there is no relationship. I think we can learn. Automation for implementing test procedures with scripts or programs This choice depends on our own preference, test environment, and allows improvements, etc., I recommend comparison with scripting or less time to do less programming or testing process. Great. If you are very proficient in programming (thinking of programming is a small dish for you, how much time does not spend more time), you can take program implementation. In order to be clearer, I think they have the following comparison:
The script has the following advantages over the program:
First, the script implementation does not require much programming knowledge, the technical difficulty is relatively small.
Second, the time taken by script is far less than the time to program implementation.
At the same time, the program has the following advantages over the script: 1. Program implementation can completely complete the automatic process.
Second, the range of automation of the program is wide than the scope of the script implementation.
In order to make everyone better agree with my point of view, I experience the fun of automation introduction, I will give an example: I have to test a monitoring module for a while, I need to do a large number of simulated users to test this module will not Have an exception, especially to simulate users to browse the common webpage, after doing two times, it feels too cumbersome and extremely bored, always open the webpage there, then close (everyone can imagine bilinguality). So I spent 10 minutes, I wrote a batch script. In the script, I used shell call IE to open all the websites I want to browse, I feel good, don't have to double-click IE with my mouse, save a lot of time, very There is a sense of accomplishment, and it has significantly improved efficiency. But this test has been tested several times, and it feels that it is a bit cumbersome. Although you don't have to click on the mouse, you don't have to enter the URL, but you have to press Alt F4 to close the open window, but also I want to squat in the test machine. Before, repeated a few times, it is indeed bored, but I am afraid that I can't turn off my open IE window (at least I don't know how to use batch). So I considered that I had to implement it with the program. At the same time, I didn't take it particularly difficult to implement, so I spent 2 days of working vacancy time using VC to write a small program, mainly using CreateProcess to open IE to browse special several Portal, then use EnumWindows and EnumChildWindows to enumerate all windows, find the IE window opened in CreateProcess, close. Oh, it's so simple, I will work every day is the upgrade monitoring module, then run my test program, then go to see the results in half an hour. This saves a lot of time for yourself, while in a shorter time, you can better guarantee the quality of testing, the most important thing is not so cumbersome. Haha!
Tell the above program implementation, there is a small episode: In the early stages of transformation I want to fully automate the test process, including the commands sent by other machines and resolve, automatically replace the upgrade data, automatically uninstall, and load the monitoring module. Open the IE browse site and turn off the IE window, even including the automatic restart machine, spend a lot of time to write a monitor and resolve the module after the command sent by other machines, it is found after the module, the automatic replacement upgrade data is too complicated, and automatically restart the machine After entering the desired system, it still needs manual selection (the test machine has a multi-set system, including the Linux system), and then only opens the IE browsing website and turns off the IE window section. This episode just wants to explain that we don't want too ideal in the process of transforming test automation. To think that users we improve is our own (there is no extensive user group), there is no need to spend a lot of time planning our improvement plan and perfect Our automation test, so we have to do short time to improve our test efficiency, make our tests become fun, using our working hours to complete such work.
Ah, I saw that our testing process is increasingly efficient, and it is also very interesting to save us to repeat the operation, it is very interesting! At the same time, the improvement of automated test is not just interesting, and can better protect the quality of the software, because the automation test can take some test cases that can be implemented, this cannot be achieved, it is not really unable to implement, according to the existing manpower Materials and our cases impossible cases, what case will be like this, maybe it is not very imagined, or a practical case: Have a test program, it can compress the PE file (similar to everyone is familiar UPX) and decompress the PE files that have been compressed, with three compressed parameters, each parameter item has 10 optional parameters, now give me test (at the same time, the developer tells me that all functions have been implemented, that is, can be in each How to measure the PE file that is compressed without this program under parameter combination conditions. Do I want to manually enter a parameter of a PE sample file that compresses a compressed collection, but there are 1,000 parameter portfolios, let alone I can't only take a sample file to test it, and I can't just do it. I don't have a mistake. Possible, I haven't encountered a programmer that does not have other errors without other errors.). It seems that I can only take other test procedures, 3 parameters are saved with 3 arrays, and then let them combine into 1000 combinations, pass each combination to the test program, so that the test program slows down to compress I collected 10,000 different PE files, I can go to www.plmm.com to see MM, haha. The company has a meal, huh, hungry, I wrote here today, I have to say "Byebye" with everyone, eat.
-------------------------------------------------- ---------CMSBAI@msn.com
