Testing can be divided into white box and black box:
Black-box testing of software means that testing should be carried out on the interface of software. In this method, the test object is regarded as a black box, and the tester completely ignores the internal logical structure and internal characteristics of the program, and only checks whether the function of the program conforms to its functional description according to the requirements of the program. Therefore, black-box testing is also called functional testing or black-box testing. Black box testing is mainly to find the following types of errors:
1. Is there an incorrect or missing function?
2. On the interface, can the input be accepted correctly? Can you output the correct results?
3. Is there any data structure error or external information (such as data file) access error?
4. Can the performance meet the requirements?
5. Are there any initialization or termination errors?
White-box testing of software is a detailed examination of software process details. This method regards the test object as an open box, allowing testers to use the internal logical structure and related information of the program to design or select test cases and test all logical paths of the program. By checking the program state at different points, it is determined whether the actual state is consistent with the expected state. Therefore, white-box testing is also called structural testing or logic-driven testing. White-box testing is mainly to check the program modules as follows:
1. Test all independent execution paths of the program module at least once.
2. For all logical judgments, "true" and "false" can be tested at least once.
3. Execute the loop body within the loop boundary and the running boundary.
4. Test the validity of the internal data structure, and so on.
The above facts show that there is a fatal flaw in software testing, that is, the testing is not comprehensive and complete. Because any program can only carry out a limited number of tests (relative to the number of exhaustive tests), it cannot be said that the program is error-free without finding errors.
In software testing and hardware testing, the earlier the intervention, the better the effect. In addition to testing embedded programs, hardware testing also needs to verify and test many aspects involved in hardware research and development, such as schematic diagram, structure diagram, component selection and so on. To ensure the correctness of each link. At the same time, it is necessary to repeatedly verify the connection of all links. Hardware is different from software, with clear interface and correct logic. The software problem will not be very big, but the hardware is different. Maybe the interface is right and the modules are right, that is, there will be many unexpected problems when connecting, especially the sequence and time of connection.
At present, it is basically done by manual testing in China. Software testing is a little more advanced than hardware testing, that is, it can carry out large-scale automated testing, especially for web software, which pays more attention to concurrent testing.
Hardware tests, such as those certified by EMC and other countries, must be verified by specialized agencies. If it is an enterprise self-inspection, there must also be relevant instruments.
By the way, remind the landlord that it is impossible to succeed if you want to do everything. Sometimes it depends on your own conditions, unless you really want to challenge, but it takes you a lot of time to study.
I also want to know a development language, scripting and code reading, as the one downstairs said. These are the ultimate focus of the test.
In addition, it is a test of human spirit. Are you willing to write code in the office day and night? Very clever.
Originally, I was doing hardware testing, not as confusing as software testing. Generally speaking, it is ok and easy to learn. I suggest you do a hardware test.