The third software engineering jobs - Preliminary Software Quality Assurance

  


 

  First, after reading textbooks and reference materials about software quality assurance What is your experience?

  Software quality assurance is a very important thing, the role of the software team must have software testing, can be a person can be completed independently tested to work with the entire team, but in the end there must be a total person in charge, if there are problems You must have a person come forward to solve, software quality assurance work is all active software team to make the software meet the quality standards defined in advance and carried out, including testing, in order to allow users to secure a perfect software experience a sense of software quality is necessary, software quality assurance process aims to make software for the management of personnel is visible through its software products and activities to review and audit to verify that the software is up to standard.

  If a software analogy to the production of a production plant. Then the production line is the process, the product produced in accordance with the provisions of the production line process. QA's responsibility is to ensure that the implementation process is to ensure the normal execution of the production line.

  In most companies, the very value of software testing, the entire project will cost seventy percent of the time on software testing test was found to lack the software during the test and correct bug, every software engineer must spend time and effort to fix quality problems existing software functions, in the book I have seen some large companies that do not need to test role, I think this is unreasonable, every software team must have some tests to test the software to find the problem, if there are problems to be responsible. 

  The final success or failure of a software is also not have to use the test to judge, but the judge is a software test the last checkpoint, not a method to improve the quality of testing, from the source code is carried out to control, good code should not need to debug or rarely needed debugging. Of course, the code does not require the code is almost non-existent, but the consciousness must be the case.

  Testing is the final guarantee of quality, if the test is missing regard the problem, we must go back to find the missing reason, improved investigation, no matter how good the rules are inadequate and the team, so the better way is to advance with the times, improved real-time , found insufficient to sum up improvements may fall once, but never fall twice in the same place.

 


 

  Second, if you are a QA project, what do you think your job responsibilities?

  Job description: testing needs throughout the software development life cycle. Complete software testing including unit testing, integration testing, validation testing and system testing. Unit testing mainly in coding phase is completed, completed by the developers and software engineers to test, based primarily on detailed testing. The interface between the main work of integration testing test software module is implemented correctly, it is based primarily on software architecture design.

  Validation testing and system testing is after the completion of software development, verification and consistency functional requirements of the software, software verification system functions under conditions appropriate hardware meets the needs of users, based primarily on user needs. Testers need to analyze software quality.

  After the test is completed, testers need to analyze software quality test results, including defect rate, defect distribution, bug fixes trends. The software includes a variety of quality characteristics are given specific measure of functionality, reliability, ease of use, security, time and resource characteristics and the like. Finally, if a software can publish or submit conclusions user.

  1. Develop test strategies, test plans, test cases, test methods according to product requirements

  2. Participate in product requirements and design reviews to ensure product testability

  3. Test execution: building a test environment, integration testing, regression testing, etc.

  4. Responsible for verifying and submitting bug

  5. Writing test reports ,

 


  Third, if you are a project manager, a full-time QA do you think that your project needs it? Or you can just have a Test? If problems arise, how do you define who should bear responsibility?

  I think that a project team must have defects dedicated testers to test the project, but still needs to be determined according to the size of the project, if only three to five people in small projects may not need QA, QA but is still a very important the role, if a problem occurs a project manager should bear the main responsibility.

Guess you like

Origin www.cnblogs.com/zdxxx/p/11565208.html