Customizing embedded type software and method for testing hardware carrier thereof
A technology of embedded software and testing methods, applied in the direction of software testing/debugging, etc., can solve the problems of conflict between the control of the test coverage and the control of the test cycle, and achieve the effect of expanding the test coverage and shortening the test cycle.
Patent Information
- Authority / Receiving Office
- CN · China
- Current Assignee / Owner
- Publication Date
- 2010-01-20
- Estimated Expiration
- Not applicable · inactive patent
Smart Images
Figure 1 Figure 2 Figure 3
Abstract
Description
Technical field
[0001] The invention relates to a testing method of computer software, in particular to a testing method of customized embedded software and its hardware carrier.
Background technique
[0002] Customized software refers to a software that is completely made according to customer needs. This kind of customized software will lead to two difficult testing situations: first, different customers have their own requirements, which will cause testers to test a large number of different versions; second, each customer will request to be able to Having a set of software suitable for oneself will lead to an extremely short test cycle for testers. Therefore, in order to meet the needs of the market, testers need to quickly and efficiently test a large number of different customer-customized software.
[0003] Embedded software is a software that runs on a specific hardware carrier. For this type of product, customers must use the corresponding hardware carrier to ...
Examples
Embodiment Construction
[0032] see figure 1 As shown, the test steps are described in detail below, and the following steps are performed in sequence.
[0033] Step 10: Prepare for the test;
[0034] Step 20: Embedded hardware carrier test; export test report analysis results, give a judgment, if successful, enter step 30, and fail, enter step 80;
[0035] Step 30: Embedded software function test; export test report analysis results, give a judgment, if successful, enter step 40, and fail, enter step 80;
[0036] Step 40: In this step, the tester can end the version test. At this point the testing process continues, but the testers are free to do other things. Enter step 50 at the same time;
[0037] Step 50: This step puts the version into use for the user. Input the version of step 40 to enter the Beta (user environment) test, which is handed over to the user to allow the user to use the product in a real environment; at the same time, the tester collects customer use reports and enters step 6...