Soft test questions

1. What are white-box and black-box tests? What is regression testing?
White box testing should understand the internal structure of the software and test whether the code correctly implements the function.
Black box testing does not need to understand the internal structure of the Software. According to the Software Requirement Specification, check whether the functions of the Program meet the requirements.

Regression testing is to check whether the changes have achieved the intended purpose, such as correct errors and adapt to the new operating environment. Second, it does not affect the correctness of other functions of the software.

2. What are the focuses of unit testing, integration testing, and system testing?
Unit testing focuses on system modules, including the correctness verification of subprograms.
Integration Testing focuses on inter-module cohesion and parameter transmission.
System Testing focuses on the operation of the entire system and compatibility with other software.

3. What are the methods and rationale for designing use cases?
The white-box test cases are designed using the following methods: basic path test, equivalence classification, Boundary Value Analysis, coverage test, cyclic test, data flow test, program plug-in test, and Variant test. At this time, it is based on the detailed design manual and its code structure.

Black box test case design methods: equivalence classification, Boundary Value Analysis, error inference, cause and scenario design. The basis is the user requirement specification, detailed design specification.

4. What qualities and skills should a test engineer possess?
Master Basic Testing Theory
Test Based on the attitude of finding out the problems with the software, that is, objective, do not appear in the image of a thorn
Proficient in reading Requirement Specification and other documents
View problems from the user's point of view
Strong quality awareness
Carefulness and responsibility
Good and effective communication methods (with developers and customers)
Previous testing experience
Timely and accurate identification of high-risk zones

5. What policies does integration testing usually have?
Big Bang integration; top-down integration; bottom-up integration; sandwich integration; hierarchical integration; Baseline integration; function-based integration; message-based integration; risk-based integration; progress-based integration;

6. What are the main functions, performance, and other features of the testing tool you have used?

7. What is the composition of a defect test report?

8. What are the factors to consider when testing a Web Information Management System?
A. Function Testing: link testing, form testing, Cookie testing, design language testing, and database Testing
B. Performance Testing: connection speed testing, load testing, and stress testing
C. Usability Testing: navigation testing, graphic testing, content testing, and overall interface Testing
D. Client compatibility test: Platform Test and browser Test
E. Security Testing

9. What are precautions for software localization testing compared with functional testing?

10. When and why does the software testing project start?
Software testing should be involved in the demand analysis phase, because the testing object is not only program code, but should be tested for all products generated during the software development process, and there is a tendency to enlarge Software defects, the later a defect is discovered, the more costly it will be to fix it.

11. What are precautions for the demand test?
A good demand should have the following characteristics:
Integrity: each requirement must clearly describe the features to be implemented so that developers can obtain all the necessary information needed to design and implement these features.
Correctness: each requirement must accurately state the features to be developed.
Consistency: consistency is not in conflict with other software requirements or high-level (system, business) requirements.
Feasibility: each requirement must be implemented within the capabilities and limits of known systems and environments.
Non-ambiguity: readers of all requirements can only have a clear and unified explanation, which is easily caused by natural operators, therefore, try to express each requirement in a concise and clear user language.
Robustness: whether the potential exceptions are analyzed in the Requirement Description and the exceptions are fault-tolerant.
Necessity: it can be understood that each requirement is used to authorize you to write the "root" of the document ". Each requirement can be traced back to a customer's input, such as use case or other sources.
Testability: each requirement should only appear in SRS once. This makes changes easy to maintain consistency. In addition, the use of directory tables, indexes, and mutual reference lists will make the Software Requirement Specification easier to modify.
Trackability: establish a link between each software requirement and its source and design elements, source code, and test cases. This trackability requires that each requirement be structured, write a statement in a well-organized manner and specify it separately, rather than a description of a large segment.

12. Briefly describe the lifecycle of a defect.

13. What are precautions for analyzing test cases )?
A. Why do I need to write use cases?
The following advantages apply to writing test cases:
Easy to communicate with the team: If a test team has 10 members, everyone is responsible for their own purposes during the test, and there is no uniform standard, the test efficiency will undoubtedly be greatly reduced; if everyone follows the unified use case specification for writing, this problem will be solved.
Easy to repeat the test: as you know, different software versions are available in the actual development process. For example, the software will be upgraded from 1.0 to 10.0. If you do not write a test case, when testing version 10.0, do you fully remember what tests you did in version 1.0? The test case is like a memorandum to facilitate repeated tests.
Easy to track statistics:
This is for the test Manager or project manager. by looking at the execution of test cases, the Project Manager can understand the current project overview, such as the tests that have been executed, what other tests are not executed, and the modules where the tests fail are mainly concentrated.
It is easy for users to perform self-testing: especially for Project software. Sometimes users want to test their own software products, but most users are non-professionals, he needs to test the product quality based on the Use Cases you have written.

Having said the advantages of so many test cases, does it have any disadvantages? One obvious drawback is that it takes a lot of time to write test cases, which is usually longer than the actual test execution time. You will have a deep understanding in your actual work.

B. When to write the use case?
Test cases should be written as soon as possible. Usually we will write test cases in the test design phase, that is, after both the requirement specification and test plan are completed.

14. What are the criteria for testing completion?
All test cases; the coverage rate reaches the standard; the defect rate reaches the standard; other indicators reach the Quality Standard