Software testing experience: 8 articles

Lessons from software testing 1

Write in front: it is not easy to find a job. I have been in Beijing for more than a month and haven't found a suita

Software testing experience: 8 articles

Lessons from software testing 1

Write in front: it is not easy to find a job. I have been in Beijing for more than a month and haven't found a suitable job yet.

When I was a junior, I failed in the computer grade exam. Because I failed in C and database, I reported to the four-level software testing engineer. After studying for a month, I did several sets of questions with the mentality of trying, and got the certificate of Band 4. At that time, I thought, this will do, it's a little wet.

I wanted to find a job in website development, but the technology is not hard enough and I have been floating in Beijing. Through a senior, I got an interview for software testing. So half a foot stepped into the door of software testing, because I just started writing test cases and haven't really integrated into the team yet.

Intern, the direct leader arranged an internship plan for me, and strictly followed it. The first thing is to read the company's software manual, understand the products and know the basic operation process of the software. If not, ask my master. So I studied for a week, which is different from using a software. In the process of using, I want to think about why this function exists and what purpose this function wants to achieve. I forgot to mention that the product is now a functional test, which is relatively simple, so it was assigned to this group. A week later, I took my teacher to check my academic performance, specific operation and some functions of the software, and then gave me a detailed explanation on several main function points and some keywords that need special attention.

Then I was given two functional interfaces to write some test cases. At first, I thought there was nothing to write. These two functions are easy to implement. I tried to write a few on the first day, and then showed them to the master, because I didn't know where to start. Although I have read some previous test cases, it is the first time to write, so I am not sure.

In this way, I wrote a few days of test cases, one function point at a time. After writing, I began to read some technical blogs, especially the writing of functional test cases in software testing. Look at some things mentioned in the blog and compare the test cases written by yourself to see if they meet the requirements. That's it. I'll modify it bit by bit.

Actually, it's quite stressful. Because the system to be tested needs to test several different databases, and different operating systems execute software, there are various learning goals, but there is still no clear goal. Work hard, since you have entered this industry, you should study hard, keep learning and make progress!

Lessons learned from software testing II

Through the practical training of this course design, I have increased my interest in learning software technology. Although I still don't know the specific content of software technology, I found the pleasure of programming from the beginning of the course c++ language. I also learned a lot of basic knowledge of computer application in the process of learning c++ language, and also got a general understanding of the computer body. Some mistakes made in the actual operation process will also have unexpected gains, and I feel that the training is very interesting. In the specific operation, the theoretical knowledge of c++ language learned this semester has been consolidated, and the basic purpose of training has been achieved. At the same time, I also found my own shortcomings, so I should pay more attention in the future. At the same time, it is recognized that c++ language has the characteristics of concise sentences, flexible use and high execution efficiency. Discover the important role of computer training, especially the deep understanding of arrays and loops.

Through practical operation, I learned the basic steps and methods of c++ language programming, developed my logical thinking ability, and cultivated my ability to analyze and solve problems. I deeply understand the meaning of "nothing is impossible, only unexpected", "unity is strength", "practice is the standard for testing truth" and "being ashamed to ask questions".

I hope to carry out more such training in the future, lengthen the design room, cultivate students' independent thinking ability and improve the practical operation level.

Through this project training, I want to thank the school leaders for providing us with this opportunity, so that we have a profound experience of going out to experience life and doing our own projects. This training made me understand that my previous study was far from perfect, and I can only learn it well through continuous efforts. I also want to thank Dana for her guidance. Although my own efforts are important, I have benefited a lot from the training and theory given by Dana's excellent teachers, which has given me a new concept and new understanding of software.

Lessons learned from software testing 3

This summer, HP sent someone to our school for software testing training. The teacher said the opportunity was rare, so I took part. To tell the truth, every day the teacher sits in the morning and afternoon, only one and a half hours of rest, which is quite tired. From the first day, we felt that class was more tiring than usual.

However, seeing that the teacher is so serious and HP is so powerful, I think all the students here are listening carefully. So people like me who never attend classes are very serious this time, hehe.

I was really tired two days ago, and I was talking about a theory class. Besides, we have never been in contact with the testing industry before, so it's hard to hear. But the teacher told us a lot about their work experience and HP's corporate culture. HP is one of the top 500 companies in the world and one of the top ten companies in the United States. I am deeply educated.

In the last two days, each of us held a notebook and operated on the computer. Our first task is to install the software, which is very big and has two G's. It took us a long time to finish the exam. The software, named qtp, is a professional version of HP's quick test. It's really a very powerful software, hehe, you'll know when you use it!

It is fun to have a computer. We surf the Internet when we have a rest. I think cats and mice have seen enough. However, that software is a big software after all, and its operation is quite complicated, and it is all in English. It is really a bit difficult for people with my English level to accept A, but I still learned a lot of knowledge, benefited from the professionalism of the teacher and remembered many words! One step closer to level 6! !

The four-day training ended completely today. In the afternoon, the teacher gave us a forum and asked us if we had any questions. As a result, we have no problem at all. The teacher taught well, hehe! We have no problem, and the teacher will tell us about his glorious history. After graduating from college, I almost didn't find a job. I studied English the most. I couldn't find a job and played games in an Internet cafe.

I remember the most emotional sentence that the teacher said was "Society is dark". We are convinced of this sentence! So in the future, work hard, no matter how dark and beautiful the society is, you can find the light, life is like this, and time is ordinary. Work hard, work hard!

The fourth experience of software testing

The importance of software testing in the whole software cycle exists in the whole project cycle, starting from the demand investigation at the beginning of the project, and the document needs to be tested when the demand specification is formed. This link occupies a large proportion in the subsequent whole project, which can lead the direction of the whole project, and its success depends on the initial decision.

Experience 1: The real meaning of software testing lies in finding errors, not in verifying whether the software is correct.

No matter how rigorous the test is, you can't completely find all the errors in the software, but the test can still find most of the errors and ensure that the software is basically available, so it is necessary to strengthen the rapid response link in the subsequent use process. Combined with the theory of software testing, the fault is found and solved actively before it is exposed to the final customer. This requires strengthening the construction of R&D team.

Experience 2: Need to pay attention to system performance testing.

Through the explanation of several cases in this training, we know that there will be many unpredictable performance problems after the system goes online, and it is necessary to simulate before going online to avoid risks, including big data access and high concurrency.

Of course, there are many kinds of coping methods, none of which can be called the most perfect. Only the most suitable one needs flexible mastery and comprehensive application to reach the optimal level. This is a field worth studying.

Here are my thoughts:

Idea 1: Strengthen the performance test before the system goes online.

At present, we don't pay much attention to performance stress testing in the process of project construction, and manufacturers rarely hire third-party testing institutions. Instead, it will be tried on the existing network, and problems will be solved again, which may lead to lag problems and affect customers' use. I hope that we can pay more attention to performance testing in the future and increase manpower input to ensure the stable operation of the system after it goes online.

Idea 2: properly participate in the research and development of related projects.

For quick response, we can't just rely on the manufacturer, but hope to respond quickly and solve the problem in time. This is also a long-term problem, and it is necessary to strengthen investment in research and development.

I personally came from a development background and had such experience. I was at the customer site at that time, because I knew the internal structure of the system, and I was able to check and solve the problem of customer feedback in the first time.

Now the system is completely developed by the manufacturer, so it is difficult to understand the internal structure, which may cause difficulties for later maintenance. Therefore, whether some projects should be involved in the manufacturer's R&D work, such as requiring the manufacturer to provide relevant elements such as source code, can enhance the maintenance personnel's understanding of the system.

Finally, thank you again for the platform provided by the company and the trust of the leaders, which gave me the opportunity to learn more deeply and show my ability. I will strive to improve the work system, improve the overall work efficiency, and provide a more solid and high-quality support service platform for the development and construction of China Southern Power Grid.

The fifth experience of software testing

The role of testing and analysis in Alipay corresponds to the role of system analysis, but one is testing and the other is development. There will be corresponding development under the department score, and there will be corresponding test case writers and executors under the test score. In other words, the test analysis document is a guide for the test executor (in my initial understanding, I think the test analyst should be the use case writer; Here, the test analyst analyzes the business, and the use case is written and executed by the use case executor.

And through this analysis, I feel that my score still has the following problems:

1, paying too much attention to the internal realization logic of development. Suggestion: treat the development of internal implementation logic as a black box, and test and analyze whether there is any problem in the development of internal implementation logic from the input and output of this black box, instead of understanding the development of implementation logic first and then analyzing it according to their ideas.

2. The analysis document is too detailed, and the steps of using examples are written out. Suggestion: Test analysis should look at the problem from the overall situation, even if the details are known, it should be left to the later use case writers to understand (just like the divided development needs to write detailed design), so that the later people will take the initiative to think about the problem.

3. Maintenance issues should be considered when analyzing documents, and specific data contents such as "R" status in repayment should not appear. Because my analysis is a guiding document for subsequent use case writers, if the margin is written like this, then the use case is likely to be written like this. In fact, neither marginal notes nor use cases should be written as detailed as R, otherwise if the development changes slightly, we will change our use cases accordingly.

4. There is no clear test purpose. When reviewing use cases, it is not suggested that each use case needs a clear test purpose, so that others can understand what is going on when they look at this use case.

Summary:

1. After writing the test analysis document, it is only based on the prd document, so the logical part of development and implementation must be abandoned (that is, don't read the division document). After the test is separated, look at the division document to see if there are any omissions in each other's consideration. Wait until the use case is written, and then let the use case author and the corresponding developer clarify more detailed things with each other.

2. Writing use cases At present, we only analyze each node in the process separately, and we will pay attention to a change in the database table when we look at the output. But in addition to the above parts, there is actually less attention to the overall process, and it is necessary to increase the coverage of each path of the business process. In the use case of path, there is no need to pay attention to the database table level.

3. Before the process path is covered, a path map should be drawn. The drawing method of this diagram should consider different entrances to draw the flow chart separately and cover the path separately.

Lessons from software testing 6

? The course "Software Testing Methods and Techniques" is taught by Mr. Zhang Jiandong. Under teacher Zhang's explanation, I deeply realized that software testing is very necessary. A software, from the very beginning of feasibility analysis, demand analysis, general design, detailed design, writing code. Under the development of this series. It took a lot of manpower, material resources, money and time to finally make the software. Try to think about it. If it is delivered to the customer, the customer suddenly finds that the software is useless or the software has great defects. The software is not easy to use and even more troublesome than the original software. The customer is very angry. The customer got angry and stopped paying. In the end, the project failed, resulting in a lot of waste of resources, so software testing is still necessary. Furthermore, software testing can find software defects, thus informing programmers to continuously improve the software. Under the condition of continuous testing and improvement. With the continuous improvement of software performance, software becomes more and more easy to use.

Software testing aims to find out the defects of software. It can be said that software testing is a kind of testing activity with the ultimate goal of finding software defects. It passes the software testing method, white box, black box, static or dynamic. Use software testing tools to find defects. Then, after defect review and confirmation, record defects, manage them with defect management tools, describe them in detail, and pay attention to the occurrence cycle of software defects. Define its severity and priority. Write a software defect report, reproduce the steps of naming defects, the expected and actual results of the test, and related pictures and text materials. Submit it to the software programmer to complete the repair of software defects.

Software testing methods include: white box testing and black box testing. Among them, white-box testing includes: sentence coverage, judgment coverage, condition coverage, judgment condition coverage, condition combination coverage, path coverage and so on. Among the black box testing methods, there are equivalence class division method, boundary value analysis method, judgment table method, causality diagram and so on. Software testing methods can be divided into static testing and dynamic testing according to whether the code is running or not. Among them, static testing includes walkthrough and code review. Dynamic testing is performed by running code. White-box testing is mostly used for unit testing of software, while black-box testing is mostly used for functional testing. Static and dynamic testing of code is necessary for every software project.

Unit testing, multi-construction pile function or driver to test. Generally, various software testing tools are used. Software testing, or program testing. Generally, unit tests are carried out first. Unit testing, after modifying the defects and errors in the unit, is integration testing. Integration testing mostly tests the function of the program to see whether the function of the program meets the requirements and is complete. The integration test is followed by the system test. System testing is aimed at the whole software system. See if the software system meets the performance requirements. So as to improve the code and meet the strict requirements of the system. Finally, the acceptance test is usually carried out in two parts. Half of them are programmers who simulate the customer environment and conduct tests. On the other hand, the other half is a test in which real customers participate. Reflect the real environment of customers to the greatest extent. In the case of trial operation, customers will see if they can find problems that can be found in normal times but can't be found in the previous environment.

Acceptance testing, including interface testing and software usability testing, uses Nielsen's ten principles to test whether the software is easy to use. Whether the software meets the user's requirements for the software interface.

Both software writing and software testing need corresponding document management. There are also test plans for software testing, software test execution and so on.

Through the study of this semester, I feel that software testing is a course that needs to be studied very much. Even as a survey course, it is a knowledge that people in the software industry must know. It is very important for software engineering projects. Now, as a student, although all the projects I have done are small projects, I still need them when the team develops together.

Testing of the project. I don't study this course very well at present, but I believe I can better experience and feel the essence of project testing and have a deeper understanding of software project testing in the future training and work. I also hope that teachers in the school can attach importance to the course of software project testing in future teaching, so that students can learn more examples, feel and understand the problems and solutions encountered in software project testing, and understand the essence of software project testing.

Lessons from software testing 7

Although writing reading notes is as usual, pen and ink are also wasted. But it hasn't happened yet to really sit down and sort out your thoughts for a long time. Because I have had a certain period of time recently, and because I have spent some time in the examination forum and downloaded and studied the electronic examination magazine on the website, my thoughts finally began to clear up, and I vaguely began to see the distant road, and I also had the courage to analyze myself and learn to look forward to the future. After all, walking in the dark feels very bad.

I think there is another important aspect that has nothing to do with technology besides learning the general technology of software testing and testing technology for a certain kind of software: business knowledge. Without specific business knowledge, it is difficult to find potential logic errors or even requirements errors in software. Of course, requirements should be based on specific software, but the depth of understanding of requirements by software testers should not be lower than that of software developers. Because all the foundations of software testing come from requirements, and all the requirements come from customers, even all of us come from customers. After identifying requirements, they must also be converted into test requirements. After all, testers still have different views on requirements from developers.

As for learning, I know that I am not a computer major and I am a stranger to the software testing industry. I have no systematic training and know nothing about software testing. I don't know what to test or how to start the test. However, you always have to know how to learn, but I think there must always be necessary ways to learn.

Find a good teacher.

This is the most important one and the best condition provided by the company. When I first came in, both td and test cases had a pm to tell you in detail. What methods should be paid attention to when designing a case? A lot of things will make you dizzy immediately. Hehe, fortunately, I understand well, and I am silent.

Learn to read

No matter what your major is, I always believe that everything will change. I know, I'm not a major in this field, but that doesn't mean I don't know this. No matter how bad it is, I came out of the book. I believe that as long as I try to master books, I can flexibly integrate into this profession and find a solution from books. Mark where you are wrong.

3. Discuss and talk with seniors.

One day, we will be seniors, but not now. At least for now, we should learn from others. Therefore, I think seniors are an indispensable part of our way forward. He will be the engine to lead us forward, give us guidance and share our work experience. However, we should also talk more. I know our predecessors have had a hard time explaining to us. After all, this is not their obligation. We should also talk more about our own views, let people know our level and facilitate the guidance of teachers and seniors.

I have learned a little from my study these days.

Experience 1: The importance of software testing in the whole software cycle.

It exists in the whole project cycle, starting from the beginning of the project when the requirements are investigated, and the documents need to be tested when the requirements specifications are formed. This link occupies a large proportion in the subsequent whole project, which can lead the direction of the whole project, and its success depends on the initial decision.

Experience 2: The real meaning of software testing lies in finding errors, not in verifying whether the software is correct.

No matter how rigorous the test is, you can't completely find all the errors in the software, but the test can still find most of the errors and ensure that the software is basically available, so it is necessary to strengthen the rapid response link in the subsequent use process. Combined with the theory of software testing, the fault is found and solved actively before it is exposed to the final customer. This requires strengthening the construction of R&D team.

Lessons from software testing 8

I ended my internship for nearly a month and bid farewell to this short internship. This time also makes me feel extremely happy and bitter. Maybe this is what internship life must go through. It seems that I have tasted the bitterness and hardship that I can't understand on campus. Therefore, I have learned a lot during this period, which has become a valuable asset in my life and an important step towards society, and it is very worth cherishing.

This internship is mainly to learn to use the application software and various products and equipment developed by the company's software department, get familiar with and understand the consistent operation methods and possible problems, and ask the old employees how to solve the problems. I was taught by an elderly employee. He told me the main points first, and then let me read them myself. Ask if you don't understand. When I first came into contact with it, I found that it was not as organized as a book, and a lot of information was mixed and dazzling, but there were different kinds. It is not enough to know what a list is casually, because I have read some books about software testing, but these are not enough at all, so I sat down to read the product introduction and manual carefully in the next few days and became familiar with its general structure.

After being familiar with the operation of related software and hardware and basic fault diagnosis, I also became a member of the work and began to try to solve some problems in customer application products. During this time, the main task is to consolidate what I have learned before, to be clear about common mistakes at a glance, and to develop serious and careful work habits. In the course of my work, I also encountered some thorny problems, but through the concerted efforts of everyone in Qi Xin, they were all solved together. After all this, I also feel that relying solely on training and listening is not so effective. Sometimes you have to try to solve the problem yourself, try to test something yourself, and find and solve the problem in the actual application process. Everything is the same as seeking truth from facts.

Combined with previous training, I know that my task now is to be familiar with the operation and data structure of various software, and then try my best to simulate, think about the application possibility in real use environment and predict the possible situation, and then compare the failure probability. After such a link, I have to do more detailed work, that is, make all kinds of test plans and test reports, then make accurate and objective evaluation of these reports and then feed back the results I get to software or hardware developers.

After studying for nearly a month, I realized that I still had many shortcomings. First, I lack work experience. Because of my lack of experience, I can't tell the priorities of many problems. Some training or study can't find the key point, and then the work attitude is still not positive enough. It is not enough to finish the assigned work in the work. If there is no work to do, I may be slack and unable to study actively. In our work, we are not allowed to be sloppy at all, and we should always keep in mind strictness and seriousness. At the same time, I don't study hard academically, which is determined by the nature of my job and my own choice, because in my opinion, only the technology recognized by the market is valuable, but after all, I am a junior and don't understand the progress of scientific research and technology, so I need more exercise opportunities.

After such practice and study, I slowly began to really understand software testing. Internship is a beginning, a place for me to learn and grow, and I feel that my work skills and dealing with people have been greatly improved.

First of all, you should be interested in software testing and have confidence in yourself. If I have these two points, I believe I can overcome any difficulties I encounter in the development process. As a software tester, you should be good at doubting. There is nothing absolutely right in the world, there are always mistakes, you are rebellious. What others think is impossible, I think it may happen, what others think is right, and I think it is wrong. Sometimes, sometimes some doubts are the key. Keep a good mood, or you may not do well in the exam. Don't bring unpleasant emotions in your life to work. In terms of work skills, because I have no experience in testing, I need to start from scratch, and I need my own efforts, patience and care. These are all my own shortcomings, but in the past few months, I really found myself making great progress. Secondly, let yourself mature a lot. Although it can't be described in words, it can be felt from the bits and pieces of life. Experience makes people grow, and experience can really make them mature.