Tools
Sorted by:
Try your query at:
 |
 |
 |
 |
 |
 |
Results 1 - 10
of
117,696
Table 2 shows the results of running each of these tests in summary form based on whether the test was satis able due to a test case error (TESTERR) satis - able due to a device timeout (TIMEOUT) unsatis able because the wrong area was being searched (UNSAT) or satis able due to the bug being found (BUG.) The rst two columns indicate case type and how many test cases there were for each case. The columns labeled \quasi-symbolic quot; report the average number of evaluations (times the simulator was run to complete all case splitting) and time for each test using quasi-symbolic values only. Note, that these were run on a version of the simulator optimized for quasi-symbolic values only. The last two columns give these same values using CD-MTBDD-based approximations.
2000
"... In PAGE 12: ... Table2 . Results of Directed Test Experiment The results show that the amount of case splitting is virtually identical for satis able tests between the two methods.... ..."
Cited by 3
TABLE III A SUMMARY OF How MANY EDGES WERE ADDED BY THE LDRG ALGORITHM, SHOWN AS A PERCENT OF IHE TOIAL NUMBER OF THE 100 CASES TESTED
Tables Secondly, systems have user interfaces and user interfaces contain objects or ridgets. Their number drives the effort required to test those user interfaces. The more objects the tester has to manipulate, the higher the test effort. As is the case with the database tables, it is easier to test many user interfaces with few objects than a few interfaces with many objects. Thus, the user interface testability is the relationship of user interfaces to objects contained therein, whereby it is assumed that each user interface has at least two objects, giving the metric
in Editors
1992
Cited by 1
Table 3: Scaling factors for -irradiations and beam tests. The numbers indicate for various dE/dx thresholds, how many particles (flux in case of beam tests) are needed per square centimetre to reach the equivalent of 1 second at LHC peak luminosity. The numbers are slightly conservative for dE/dx below 78 keV, since low energy neutron interactions have not been taken into account for the beam tests.
"... In PAGE 25: ...The conclusions to be drawn from Table3 are: -irradiations: If the critical dE/dx values are below 78 keV/500 m (up to 400 times the average loss of a minimum ionizing particle), then -irradiations are a good tool for testing the chambers. The scaling factor depends on the exact dE/dx threshold, but has a minimum of 74, when the critical dE/dx for the chamber is just below the average ionization loss of the injected .... ..."
Table 4. Test cases for the SPEDI framework.
"... In PAGE 5: ... Many of these cases stress multiple different features simultaneously. These test cases, their descriptions, and results are displayed in Table4 . The results in the table are the expected outcome of the test.... ..."
Table 5: Average NumberofTest Cases Per Set
1994
"... In PAGE 10: ...92 0.76 Table 4: NumberofFaults Found by Mutation-Adequate and Data Flow-Adequate Test Data 6 TEST SET SIZE Table5 gives the average number of test cases for the mutation-adequate test sets and the data #0Dow-adequate test sets for each program. The most obvious observation is that in most cases, mutation requires many more test cases than data #0Dow does.... ..."
Table 1. Test Suite and Statistics about Strongly Connected Components (SCC). For the test cases there were very few (no more than 3) SCCs containing more than one class. On the other hand, those few SCCs can be very large, containing nearly 5000 edges in the case case of the Drawserv test case. The matrix test case, listed on line 3, did not contain any cycles, although there are self loops for some of the classes; some classes contain as many as four (4) of these self loop edges, as illustrated on the third row, last column of data in this table.
Cited by 1
Table 2: Average NumberofTest Cases Per Set
1992
"... In PAGE 9: ...For the other four test sets we #0Crst generated as many test cases as possible using Godzilla #28 the same procedure as for the other experimental programs#29 and then for the adequacy calculations added the quot;strong quot; test case mentioned above, that killed the rest of the mutants. Table2 gives the average number of test cases for the mutation adequate test sets and the data #0Dow adequate test sets for each program. The most obvious observation is that in most cases, mutation requires many more test cases than does data #0Dow.... In PAGE 12: ... The only program for which the mutation adequate test sets were not data #0Dow adequate was regula. Table2 shows that the average number of test cases required for the data #0Dow adequate test set for regula is 23.8, which is slightly more than the average number of test cases required by the mutation adequate test sets.... ..."
Table 3 b) Without a priori knowledge of the shape of the solution In the most general case, we do not have a priori information on the shape of the solution. In order to nd the optimal solution, many paths must be tested which can have very various shapes.
Table 2 is an example of an C7BTB4BLBN BGBN BFBN BEB5. Although the use of orthogonal arrays for testing has been discussed in the literature [2, 27] these may be of less interest in component testing because they could lead to overly large test suites with AL BQ BD. For cases of DA and CZ where an orthogonal array with AL BP BD does exist, clearly this is the optimal test suite. However, there are many val- ues of DA and CZ where an orthogonal array with AL BPBDdoes
2003
"... In PAGE 2: ...Browser OS Connection Printer 1 NetScape Windows LAN Local 2 NetScape Linux ISDN Networked 3 NetScape Macintosh PPP Screen 4 IE Windows ISDN Screen 5 IE Macintosh LAN Networked 6 IE Linux PPP Local 7 Other Windows PPP Networked 8 Other Linux LAN Screen 9 Other Macintosh ISDN Local Table2 . Test Suite to Cover all Pairs from Ta- ble 1 four way interactions.... ..."
Cited by 23
Results 1 - 10
of
117,696
