Time passes, never stop, a period of time has ended, review this period of time since the work, the harvest is quite fruitful, it is time to take the time to write a job summary. You have seen the work summary should be what kind? The following is my carefully organized software test engineer probationary period transfer work summary, only for reference, I hope to be able to help you.
Software test engineer probationary period transfer work summary 1
With the full and compact work life, two months have passed. In this period of time there are gains in work, knowledge, experience growth, while also exposing many problems and deficiencies. Summarize the experience, learn a lesson, this paper will mainly from several aspects to summarize the work: the main content of the work; the failures and lessons learned as well as successes and experiences; look forward to the next stage of the work, to determine their own goals. To serve as a record of punishment to prevent the aftermath.
1, the main content of the work
In these two months of work, my overall task is to help xx do a good job in the Armed Police Force xx xx management system of the late test, coding, modification, document preparation work, after the decomposition, I mainly do three things: writing xx system of various types of documents; the system coding and bug errata work; system coding and bug errata work. I mainly do three things: write all kinds of documents for the xx system; code and bug errata for the system; and test the system. The following is an introduction to my work according to time.
The first step into the workplace, into the professional software manufacturing company, for me, a newcomer who has not been exposed to the standard software production process, the start is a big problem. If you do development directly, the business is not skilled, the code is not standardized, the disadvantages outweigh the advantages; if you only do learning, you can not keep up with the pace of the project, can not be the fastest speed into the work.
I was still apprehensive about what I was going to do, and the task was given to me, first of all, to carry out the testing of the xx system. The advantage of this is that in the process of testing, to understand the overall layout of the project, to understand the business logic of the project, to understand the project has not yet completed the work and as the next stage of the work objectives. So, onboarding is off to a great start.
In the xx system after the test, exposed the system's many problems, the test process found that the xx system does not have input qualification, in order to solve this problem need to organize the whole system data, my next task is to write the xx system data requirements document. In the process of writing this document, a more in-depth understanding of the xx system, for the subsequent bug errata work to lay a certain foundation.
After completing the preparation of the data requirements document for the XX system, the new task is to qualify the input data for the entire XX input data, which is extremely difficult at the beginning of the task, and fortunately, we have the help of our colleagues in order to successfully complete the task. The task was completed, but the half-understanding of the input qualification method and the lack of care in the task completion process also sowed the seeds of the problems that occurred later.
After adding input qualification to the XX system, we entered the phase of solving minor program problems, making minor patches to the XX system. This time is more study than work, different problems urge me to daily and Baidu intimate contact hundreds of times, but also to bother your colleagues in the busy colleagues to take the time to give me help. I've been working on this for a while now, but I'm not sure if I'm going to be able to do it.
After completing the system's 'repair,' our program was sent to XX for the first round of testing, and during the week of testing, I was mainly supplementing my knowledge of the basics of network programming.
After the results of the first round of testing came out, our project team started an intense first round of bug errata for the xx system. After I got the bug list, I realized that half of the bugs were caused by me, and there were a lot of input qualification problems, so I took the initiative to take on the input qualification part of the bug errata work.
After the completion of the first round of bug errata, the first round of regression testing, the test results have been unsatisfactory, there are still a lot of problems that need to be modified, and many of the problems are still due to me, there are still a lot of problems with the input qualification, and once again, after the modification, our program was sent to the fifteenth for the inspection.
In addition to the testing, I was given a new task, to complete the outline design of the XX system, as well as the writing of the detailed design document. These two documents were completed on September 2nd.
At this stage, my task is to regression test the mineral rights system against the list of bugs examined.
2. Lessons learned from failures and successes
Lessons learned from failures should be absorbed, and successes should be summarized. My definition of success is: the completion of a set program or goal under the premise of quality assurance is success. All other outcomes are failures.
Successful experience:
(1) Dare to accept the task and want to do everything possible to complete
The biggest gain in two months of employment is to dare to accept the task and want to do everything possible to complete the task, each task for the first time in the workplace for me is a challenge, how to complete the task of the quality and quantity is the most basic requirements. The biggest success in these two months is that none of the tasks were procrastinated, and every time I did my best to complete the task.
(2) the courage to bear the error, face up to their own problems
In these two months of work can be said to be a constant error, from the document of the typos of this small problem to the xx system bug modification incorrectly lead to the collapse of this big mistake, exposed a lot of problems, I adhering to the error that is to be corrected, the next is not an exception to the idea, to face up to their own mistakes and actively correct, so this is also regarded as a I've made a lot of mistakes, and I've been able to fix them.
Lessons of failure:
(1) pay attention to every detail, do not ignore the small problems
In the initial xx system data requirements document preparation process, the data of some pages in the database is not stored in the case did not pay attention to the data qualification in the later stages, but also to re-modify the data requirements document, resulting in an unnecessary waste of time. Waste of time. The lesson to be learned from this is not to let go of any small problem, which may lead to big problems later.
(2) Repeated work can not be careless
In the xx system for input qualification method is familiar with, are repetitive work, to each page, each field for input control statements to add, in the pages after several pages, there are some pages do not add a complete, or prompt the incorrect statement, in the subsequent bugs errata appeared in a large number of such problems, wasting a lot of time. A large number of such problems, wasting a lot of time and effort to modify. The lesson we learned from this is that we can't be careless in our work, and we have to do a good job in repetitive work. General repetitive work the first time to do a bad job, the follow-up check is a very waste of time to modify.
(3) consider the problem to be rigorous
In the process of the XX system bug errata, the input qualification conditions of the judgment problem, I take for granted in accordance with my subjective ideas on the data qualification, and in the regression test when the problem, these are the consequences of the consideration of the lack of rigor. The lesson of this matter is that the lack of rigorous consideration directly leads to the problem of pushing back, affecting the efficiency of the work, and it is very easy to bury hidden dangers.
(4) focus on user experience
In the process of xx system bug errata, the most modified in the coordinate system prompt statement, because the coordinate system not only requires that data must be filled in, and each data has a strict format qualification, so each error prompts the pop-up in the spirit of how to let the user know where to set up for the principle of error. In the initial qualification, the statement is rough, the pop-up statement is not clear, resulting in the use of the user's inconvenience, but also to re-engineer. The lesson of this problem is to consider the issue from the user's point of view, and focus on the user experience from a simple prompt statement to start.
3, looking forward to the next stage of the work
The next stage of the short-term our work is mainly for the use of mineral rights system database changes to modify our system. My task is to learn the difference between oracle and sql databases, and do a good job of migrating from sql databases to oracle databases.
These two months of work life is full and fun, met a lot of colleagues and friends, the company's atmosphere is very relaxed and happy. Thank you for two months xx manager's concern, thanks to the department colleagues of the careful guidance, thanks to the company's colleagues enthusiastic help, I hope that in the next work can be punished before to prevent after, summarize the experience, learn a lesson, to do personal and the company *** glory and shame of the same forward and backward, *** with the realization of the splendor of the Middle Kingdom.
Software test engineer probationary period to correct the work summary 2I entered the xx company since x month x day to engage in cell phone software test engineers, in the unknowingly has passed 2 months of probationary period. In this period of time, I feel a lot, although this is not my first job, but during this period, I have always been modest and prudent for the work, serious and responsible attitude, has never changed.
In the work of this department, I have been strictly demanding of myself, seriously and timely completion of each task set by the leadership, and learning from colleagues, and constantly correct the shortcomings of the work; with the implementation of the various departments responsible for the completion of the company's work,
In the past two months, through continuous learning and self-improvement, has adapted to the work of the job, but for a newcomer into the company, to fully integrate into the enterprise, the company will not be able to provide the necessary information. But for a newcomer to the company, to fully integrate into all aspects of the enterprise, may not be comprehensive enough in the consideration of a number of issues, but I believe that, through the company's leadership and colleagues of the careful guidance, I will be in the future work to better improve their own level, quality, and better fulfillment of their jobs.
In the future work, I want to continue to work hard to overcome their shortcomings, make up for the shortcomings, to the white box testing, internal code testing direction to understand, strengthen the software testing, computer language knowledge, and continuous self-learning, and strive to become a learning, innovative, hands-on both of the new century talents.
Software test engineer probationary work summary 3This four-month internship and probationary period, so that I have an in-depth understanding of the work of cell phone software testing, is to do their best to find the shortcomings of the test phone, after the developers to solve the problem so that the phone as soon as possible to meet the standards of the market, the bugs found is to create value for the company. As a four-month employee of xx, I also have a certain understanding of the company, xx Technology Co., Ltd. is a trusted provider of consulting and technology services, the company has a strong global operational capacity, strict quality standards and efficient delivery process, is committed to becoming a global enterprise "partner in the new era" for the success of the customer! We are committed to being a "partner for the new era" for global enterprises and to the success of our clients. Since 19xx, xx has been committed to providing global clients with world-leading business/it consulting, solutions and outsourcing services. xx has accumulated rich industry experience in financial services, high-tech, telecommunications, tourism and transportation, energy, life sciences, manufacturing, retail and distribution, etc. Our major clients include many Fortune 500 companies and large and medium-sized Chinese enterprises. The XX branch where I work mainly undertakes Nokia cell phone testing tasks, and has been highly recognized by the XX company in its past testing work.
First, the work of the advantages and shortcomings
For the failure of the lessons to be learned, the success of the experience to be summarized. My definition of success is: to complete the established plan or goal under the premise of quality assurance is success. All other outcomes are failures.
Strengths:
(1) Dare to accept the task and do everything possible to complete it
Four months into the job every task for the first time I am a challenge to complete the task is the most basic requirements, even if they are not familiar with the task will do their own efforts and seniors to help complete on time.
(2) the courage to bear the error, face up to their own problems
In the four months of work made some mistakes, the use of testing tools is not skilled, resulting in test results fill out the irregularities, etc., I adhered to the error that is to change, the next is not an example of the idea of facing up to their own mistakes and actively corrected.
Inadequate:
(1) Due to the work time is not long, participated in a lot of training, in the testing of these knowledge is not skilled enough to use, so the cell phone in the bug found
number is not high.
(2) At the beginning of the work, the use of some testing tools is not very skillful, in the process of using the delay in some of the work of the time, leading to their own in the specified time to complete the task is more nervous.
Second, the future work to improve
(1) pay attention to every detail, do not ignore the small problems
Do cell phone testing work, the first thing you need to have is to be careful, the only way to find the phone bugs, can not let go of any one with the test case description of the implementation of the results, no matter how small the difference.
The first thing you need to be able to do is to be careful, so that you can find bugs in your phone.
(2) Repeated work can not be careless
Mobile phone testing, sometimes the same test case to repeat the test on different phones, which is quite a test of my patience, every time you do test cases to the first time to do so, carefully implement each step of the operation.
(3) Consider the problem to be comprehensive
Every time you do the task to have some free thinking test, which requires us to consider the problem to be comprehensive to expand the thinking to do as much as possible to test, in order to find more bugs.
(4) Strengthening of the study
There are usually time in addition to participate in a variety of training in addition to the training after the review summary. But we also need to review and summarize in a timely manner, to find their own do not understand the place in a timely manner to master or experienced people to teach, to improve their testing skills, and to seriously study the test tools, more practice using them to ensure that they reach the level of proficiency.
Third, the next step in the work outlook
The next stage of the work I am very confident that it will be improved over the previous, after four months of work and learning has been equipped with a number of useful experience, I believe that they will be a great help to my future work. In the future, I hope I can improve the number and quality of bug reports, and in addition to this, I have to continue to learn more ways to improve my ability to test cell phones with my masters and seniors.
These four months of work life is full and fun, met a lot of colleagues and friends, the company's atmosphere is very relaxed and happy. Thank you for four months xx team leader's concern, thanks to the department colleagues of the attentive guidance, thanks to the company's colleagues enthusiastic help, I hope to be able to punish the next work before to prevent after, summarize the experience, learn from the lessons, to do personal and company *** honor and disgrace with the advance and retreat, *** with the realization of the brilliance of the xx.
Software test engineer probationary period corrective work summary 4Through the interview, came to xx company work, has been a month past, I try to understand the company's culture, system, related to the work of the post of a variety of information, in order to as soon as possible into the company's family. My work in the past month is summarized as follows:
First, the company's understanding
In the early stages of the work, I understand the development of the company from various channels; on the company's business model, organizational structure, geographic distribution of the initial understanding; read some of the company's management system. I am confident about the company's development prospects and am willing to grow more solidly with the company***.
Second, the work of understanding
1, information technology work without medium-term strategic objectives
Infrastructure and operation and maintenance, infrastructure is weak. Equipment corresponding asset information, application rights, auxiliary security, extended applications, management are loose, the lack of a full set of practical operation and maintenance mechanism (of course, this is related to the company's previous no talent in this position).
3, network
network is not enough to support the current scale of the company's applications, in: network structure without planning, insufficient bandwidth, network management equipment performance is too low, these factors lead to the company's network is not stable, can not support the release of IT application services.
System promotion
For the current xx system in the test preparation stage y appreciate some of the problems:
(1), from the overall point of view of this set of xx does not meet the current management structure of the company. That is: my company selected this xx system for small and medium-sized enterprises or but the organizational structure of the enterprise, not suitable for our current group management structure. In the future we xx application gradually mature and gradually deepen the level will leak out a lot of problems. Such as: with the future of the group type other system data interface, deeper level of authority delineation
(2) of the module selection is unreasonable. For general xx very useful module did not buy, such as: schedule reminders, digital signatures, mobile applications. For our current status quo is not necessary module and bought, such as: mail module, office supplies management.
(3) weak system functions. Open self-service modification of the place of the relative market mainstream xx less; collaborative approval process set up troublesome; News Center layout is rigid, can not be modified; Knowledge Center layout lack of humanization; address book function is very weak; instant messaging function is too poor
(4), the system implementation planning is not comprehensive enough. The system implementation is fragmented and lacks overall planning. Such as: the system infrastructure equipment set up insecure; data backup is unreasonable; some of the system's basic data lack of uniform rules developed; B consultant replacement of ordinary, docking people.
Third, the work to promote
1, the two wireless routes installed and used.
2, on-line preparation work is completed. As of xx month xx xx on-line preparation is basically completed, including pre-launch training for all staff. The next step is to start the trial line of the company, and then continue to coordinate and deal with the problems that arise after the on-line operation.
3, machine room organization, will be a small UPS loaded to the financial use; do not have to clean out the machine room;
Fourth, the work unfolds the plan
Through the company's understanding of the use of existing resources, the task has been clearly defined as the first (xx system implementation to the whole company), combined with the company's information technology for the long term development, and gradually From the infrastructure to improve the work of information technology, plans to work as follows:
1, first of all, the xx system will be implemented at the headquarters of the Group.
2, the next step to rectify the server room, so that the server room is relatively safe and clean.
3, an in-depth understanding of the entire group of companies in the use of the network, the network of comprehensive planning and transformation, for the future of the company to prepare for more IT applications.
4, the establishment of upgrading and the establishment of basic information **** enjoy communication, namely: upgrade mailboxes, the establishment of the entire group can be applied to the instant messaging system, simple file **** enjoy.
5, to build a preliminary information management approach.
The system is gradually implemented in each company to use up.