1. First of all, it is usually a rather old-fashioned question: tell me about your experience.
HOHO .. I think everyone has been asked this question. Pay attention to the key points. Don't be nervous. Speak slowly.
You can cut to the chase immediately after the old saying. According to your experience, what is your understanding of software testing/quality assurance?
This is a matter of different opinions, and it is basically something in books. It would be great if I could have some unique ideas of my own, hehe.
3. After you understand it, of course, you should ask if you understand software testing. It's your turn to ask what is the process of software testing, and what is the process of your original company?
The previous question is still something in the book, which generally introduces soft testing. In fact, ordinary domestic small and medium-sized companies simply can't meet the test specifications mentioned in the book, and the test process is the same. There is no way.
This is our whole big test environment now. Just follow the instructions in the book. The latter knows what to do and tries to express the testing process of the original company concisely.
4. Then you can have many questions, many of which depend on your own test experience and understanding of the test, such as:
(1) Your understanding of SQA's responsibilities and work activities (such as software measurement):
SQA is a project team independent of software development. By monitoring the software development process, ensure that the software development process conforms to the specified CMM process (if there is a corresponding CMM process), and put forward nonconformities in time.
To discuss and improve the plan, it is necessary to ask the senior manager to report the solution to the problem. This can prevent the introduction of defects, thus reducing the maintenance cost of the later software. The main work activities of SQA include formulating
SQA work plan, participate in the product review, and review the process quality, functional configuration and physical configuration; Measure the data generated during project development, etc.
(2) Tell me about your understanding of software configuration management:
In the process of project development, configuration items (including products at various stages) should be controlled by corresponding configuration management tools, and the use of configuration management depends on the project scale, complex performance and risk level. software
The larger the scale, the more important configuration management becomes. In configuration management, there is a very important concept, that is, baseline, which is the combination of various configuration items at a certain stage, and a baseline provides a formal standard.
Subsequent work is based on this standard, which can only be changed after authorization. Configuration management tools mainly include CC, VSS, CVS, etc. I've only used CVS occasionally, and I'm not familiar with others.
(3) How to write test plans and test cases:
Simply put, the test plan should have detailed test strategies (test methods, etc.). ) and reasonable and meticulous resource arrangement. As for test cases, it depends on whether the requirements (including functional and non-functional requirements) are refined to functional points.
, whether it can be tested.
(4) Talk about the general situation of mainstream software engineering ideas (such as CMM, CMMI, RUP, XP, PSP, TSP, etc.). ) and your understanding of them:
CMM:SW Capability Maturity Model Software Capability Maturity Model, which is used to improve and evaluate software processes and evaluate software capabilities.
CMMI: Capability Maturity Model Integration Capability Maturity Model Integration CMMI integrates most of the latest software management practices and makes up for the defects in the SW-CMM model.
RUP:rational unified process is a software engineering process. It provides a standardized method for assigning tasks and responsibilities in development organizations. Its goal is to ensure the most satisfactory.
Personally, the core idea of high-quality products required by end users is development iteration, and each company can tailor RUP appropriately according to its own software development process and the characteristics of the project to be developed, and make symbols.
Conform to your own software development process.
XP: Extreme program, which means extreme programming, is suitable for software development of small teams. If you want the third question above, you can use this development process in combination with the prototype method. Understanding testing is very important for xp development.
Importance, emphasizing the concept of testing (focusing on unit testing) first. Programming can obviously improve the quality of code, and continuous integration is very beneficial to quickly locate problems.
PSP and TSP are individual software processes and team software processes respectively. As we all know, CMM just tells you how to do it without telling you.
How did you do it, so PSP/TSP tells you how to do it in the process of implementing CMM. PSP emphasizes building personal skills (how to make plans, control quality and cooperate with others, etc.). ), while TSP emphasizes.
Produce and deliver high-quality software products (how to effectively plan and manage project development tasks, etc. )
In a word, simply implementing CMM can never really improve the capability maturity. Only by organically combining the implementation of CMM with the implementation of PSP and TSP can it exert its greatest effectiveness. Therefore, the software process framework should be
Organic integration of CMM/PSP/TSP.
(5) Understanding and practical experience in project management, white-box testing, unit testing, automation testing, performance testing and stress testing tools. (In fact, it is basically MI and Rational tools):
It depends on the individual, so I can't say.
(6) Other specific technical knowledge (such as knowledge of various computer languages and databases). );
5. Also, how do you ensure the software quality, that is, how do you think the software quality can be guaranteed to the greatest extent?
Testing can't guarantee the quality of software to the greatest extent. The high quality of software is developed and designed, not tested. It not only makes all stages of software development pass the monitoring of software development process.
Each link should be carried out according to the prescribed procedures. By reviewing the products at each stage, QA monitoring the process and auditing the functions and configurations, the development can be optimized. Of course, testing is also an important way to ensure the quality of software.
Type is an important part of software quality assurance project.
6. Then, based on the current national conditions in China, most companies are short of software projects, with few personnel, and there is no or very no standardized requirements document. How do you think to ensure the quality of the software in this case?
? What most companies want to know is how to ensure the quality of software in the face of such difficulties, because these companies generally do this-don't want to invest too much, want to ensure the quality, dizzy.
In the above situation, it is almost impossible to improve the quality of software only through testing, because there is not enough time for you to test, and the lack of standardized documents leads to the failure to refine the test requirements.
And conduct targeted tests. Therefore, as the company's quality assurance, you should determine the software life cycle model (such as RUP cutting and prototyping) that is most suitable for the project itself, and make clear the development of the project.
Process and urge the project team to work according to this process. All project team members (more importantly, the project manager) should make a reasonable work plan, strengthen the unit testing of the code, and standardize the product delivery date set by customers.
Within the scope of continuous product integration, etc. If time permits, we can cooperate with customers to carry out necessary system function tests.
7. It's almost time to ask some questions only related to software testing, such as:
(1) How do you think you can become an excellent test engineer? Dizzy, this question seems to be necessary, and the answer is nothing more than what comprehensive technical ability and meticulous logical thinking are needed.
D, excellent communication skills, but also skepticism, sense of humor, insight, etc. What do you mean by excellent? You have all the abilities you should have and all the abilities you shouldn't have, and they are all excellent. This is excellent, hehe.
Just kidding, anyway, this question is almost like this, and the specific requirements are everywhere on the Internet.
(2) There are others, such as the evaluation of their own advantages and disadvantages, career ideals, why they left their last company, what impressed them the most in their career, whether they can travel and work overtime, whether they can withstand pressure and challenges, and salary.
Water requirements, when can I go to work, and other questions that have to be answered in the interview can only be done by myself.
(3) Another important issue is language ability, especially English proficiency. In this case, the requirements of each specific company are different, and there is nothing to say.
That's about it. If necessary, you can Google it specifically. Hoho is for reference only!